JTS server goes down with error : CRJAZ1413E A connection to the database could not be acquired in 3000 ms.
JTS log-
ERROR repository.service.internal.
rdb.JDBCConnectionPool - CRJAZ1413E A connection to the database could not be acquired in 3000 ms. This can happen if your server is under very high load, or if your DB server is not powerful enough to quickly process the requests from this server. The primary resolution to this problem is to use a more powerful DB server. If this problem is intermittent, increasing the JDBC Connection Pool Size or JDBC Connection Pool Wait Time properties in the Advanced Properties page might help you avoid the problem in those rare cases.
JTS version 3.0.0.1
No error on SQL DB log.
4 answers
This is a known issue in 3.0.1, upgrading to 3.0.1.3+ should fix the issue.
Comments
Why the issue started suddenly in this version as our team was using that from last 6 months?
We can upgrade to 3.0.1.3 but it really solves the issue as I still don't know the root cause of it.
No idea - we had exactly the same behaviour, had been using 3.0.1.2 for quite a while and suddenly started seeing this issue.
Hi Raj,
Is this happening frequently? If there are no errors in the SQL Server error.log, then the likely cause is latency between the DB and CLM server. Can you also confirm the version of CLM you are using? Is it 3.0.1? Does increasing the Connection Pool Wait Time to a value like 10000 help, or does it still time out then?
Is this happening frequently? If there are no errors in the SQL Server error.log, then the likely cause is latency between the DB and CLM server. Can you also confirm the version of CLM you are using? Is it 3.0.1? Does increasing the Connection Pool Wait Time to a value like 10000 help, or does it still time out then?
I believe some jobs such as data collection jobs are scheduled over night. You might want to check the scheduled times in the advanced properties.
Are you running the whole deployment? I have seen cases where the operations/infrastructure teams quiescence databases e.g. for backup over night. I would try to look into if there is something like tat happening too.
In general look at the etl logs, general CLM logs.
Are you running the whole deployment? I have seen cases where the operations/infrastructure teams quiescence databases e.g. for backup over night. I would try to look into if there is something like tat happening too.
In general look at the etl logs, general CLM logs.