CloverETL is now CloverDX - Learn Why

Prevent Derby from installing/running

Support questions related to CloverDXServer

techypaul
Posts: 1
Joined: Wed Dec 27, 2017 4:43 pm

Prevent Derby from installing/running

Postby techypaul » Wed Dec 27, 2017 4:50 pm

Hi,

Is it possible to remove Derby entirely, or prevent it from running?

Code: Select all

2017-12-27 15:39:24,620 [localhost-startStop-1] INFO  com.cloveretl.profiler.server.app.ProfilerDataSourceFactory - Using JDBC connection: jdbc:derby://localhost:22649/databases/profiler;create=true (org.apache.derby.jdbc.ClientDriver)
2017-12-27 15:39:24,658 [localhost-startStop-1] INFO  com.cloveretl.profiler.server.app.InbuiltDatabaseManager - Booting internal Apache Derby database
2017-12-27 15:39:24,680 [localhost-startStop-1] INFO  com.cloveretl.profiler.server.app.InbuiltDatabaseManager - Starting Derby Network Server Control
2017-12-27 15:39:24,765 [localhost-startStop-1] INFO  com.cloveretl.profiler.server.app.InbuiltDatabaseManager - Apache Derby start issued
Wed Dec 27 15:39:24 UTC 2017 : Could not connect to Derby Network Server on host 127.0.0.1, port 22649: Connection refused (Connection refused)
Wed Dec 27 15:39:24 UTC 2017 : Apache Derby Network Server - 10.11.1.1 - (1616546) started and ready to accept connections on port 22649
2017-12-27 15:39:25,283 [localhost-startStop-1] INFO  com.cloveretl.profiler.server.app.InbuiltDatabaseManager - Apache Derby started


We're using MySQL and Derby is unwanted.

Thanks,
Paul.

jandikovae
Posts: 41
Joined: Fri Nov 04, 2016 8:51 am

Re: Prevent Derby from installing/running

Postby jandikovae » Wed Jan 10, 2018 4:59 pm

Hi Paul,

Thank you very much for your question. In fact, the Derby instance that you can see in the log file has been initialized for CloverETL Data Profiler.

This application is maintained independently from the CloverETL Server and a separate database is created for it by default. Even though you are using MySQL DB for CloverETL Server, the CloverETL Profiler is still using the default Derby DB.

Once neither the Server nor the Profiler uses the Derby DB driver, there is no need to disable the unused Derby database explicitly, the Derby shouldn't start on its own.

For more information about how to configure Data Profiler DB please see the following page: http://doc.cloveretl.com/documentation/UserGuide/index.jsp?topic=/com.cloveretl.profiler.doc/docs/reporting-console-configuration.html

I hope the information provided was helpful. Should you have any additional questions, don't hesitate to ask. Have a nice day, Eva
---
Eva Jandikova
CloverCARE Support
CloverDX

Visit us online at http://www.cloverdx.com


cron