"APPARENT DEADLOCK" Errors in the Logs

ISSUE:  

We are continuously receiving "APPARENT DEADLOCK" errors in the logs of the Adeptia Suite 6.0 version that we have installed in our test environment:

ERROR:  

va:608) - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@5c934917 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

2013-04-11 15:44:52,749 WARN [Timer-1] com.mchange.v2.async.ThreadPoolAsynchronousRunner com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector.run(ThreadPoolAsynchronousRunner.java:624) - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@5c934917 -- APPARENT DEADLOCK!!! Complete Status:

2013-04-11 15:44:52 log4j:ERROR error during logging. INSERT INTO AU_LOG (AU_ID, AU_LOGDATE, AU_PRIO, AU_CAT, AU_THREAD, AU_THROWABLE, AU_LOCATION, AU_USERID, AU_GROUPID, AU_MSG) VALUES ( 136571309275077,'1365713092750', 'WARN', 'com.mchange.v2.async.ThreadPoolAsynchronousRunner', 'Timer-1', '', 'com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector.run(ThreadPoolAsynchronousRunner.java:624)', 'null','null','com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@5c934917 -- APPARENT DEADLOCK!!! Complete Status:


REASON:  

The above issue occurs due to Log Connection Pooling. The pool waits indefinitely (when there are no available connections) for a connection to be returned.

 

SOLUTION:

GOTO location ".\AdeptiaSuite-6.0\AdeptiaServer\ServerKernel\etc" and open "server.configure.properties" file. Search for a property named "abpm.logdb.pool.maxWait" of Log Connection Pooling and change its value from -1(indefinitely) to a value in milliseconds say 300000.  Refer below image for more details:

                                         Screenshot_1.jpg

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.