Datawarehouse connection error
Yesterday I installed the Jazz Reporting Server (JRS) v5.0.2 in a computer and the setup runs without problems: data sources were connected succesfully and I was able to run some custom reports. Everything worked fine.
Today, I have followed the same installation procedure in other computer and I am getting the following error when attempting to connect to the datawarehouse:
A com.ibm.team.integration.reporting.db.exception.DbAccessException error has ocurred when validating the connection to the database, caused by !CRRGW6018E Server could not connect to database: "//localhost:1527/conf/jts/derby/warehouseDB" Exception: "CRRGW6003E Server could not connect to the database because the connection settings are not valid or because the database is not accessible (SQLSTATE:08004, SQLCODE :40,000). Check the connection values in the data source."!.
I have checked the connection parameters but I cannot find the problem source. All the parameters seems to be okey.
Does anyone knows which could be the solution?
Thanks in advance,
Leire.
Accepted answer
Comments
Thanks for the quick reply.
How can I know if the database is started? The tomcat server is started from a windows scheduled task, might this have something to do with the problem?
I don't know any easy ways the check the status or the log files of the embedded Derby database, unfortunately. If the database is started, port 1527 should be open, according to the configuration. Starting Tomcat as a Windows service should not cause such problem.
It seems that restarting the machine solves the problem. Apparently, when the scheduled periodic task that stops the JTS is executed, something (as you said, probably the database connection) gets stuck.
But each time the JTS is stopped, the connection breaks and the same error appears... What should I do?
Thank you for all your assistance.
One other answer
Comments
I think I missed your comment (follow-up question) two weeks ago. The Derby database that comes with CLM is an embedded one. It means that it only starts with the application (JTS in this case). So if the applications stops, the Derby database stops; if the application restarts, the Derby database restarts; and so on. Of course when the database stops/restarts, all existing database connections are lost. The Derby database is not intended for production use, and you should use an enterprise database (DB2, Oracle or SQL Server) for this purpose.
Thanks for your suggestion. I will take that into account!
Just to make it clear for future deployments… I understand that the database that comes with CLM is an embedded one, and so, it starts with the JTS. The JRS also starts with the JTS. I also understand that if the JTS is stopped, the DB and the JRS are stopped too, and so, all the connections are lost. Until now everything is clear and coherent.
What I cannot understand is why the database connection cannot be reestablished after restarting the JTS. As you said, after restarting the JTS, the DB and the JRS are restarted too. Even if the current connections are lost, the DB configuration is saved in the JTS (isn´t it?), and that is why I cannot understand why the connection cannot be reestablished. This does not happen when I restart the PC (in this case, the connection can be reestablished).
To summarize the situation:
- Start the JTS/JRS/DB, after the first JTS setup the connection with the DB is OK.
- Stop and Start JTS/JRS/DB, the connection with DB is NOT OK.
- Stop JTS/JRS/DB, restart the PC and Start JTS/JRS/DB, the connection is OK again.
My apologies for being so persistent and thanks a lot for the assistance.
I suspect that in your case 2, there are lingering network connections. Wait long enough and see if you still have the problems. To check connections connecting to a certain port (1527 in this case), run the below commands:
On Windows:
netstat -aon | findstr 1527
On Linux:
netstat -pant | grep 1527
We didn´t realise that in this specific setup DWA was also running and it was using the port 1527 for its derby database.
We have changed the JTS datawarehouse database port and the error is solved.