Possible deadlock in the EMS Java client libraries.
Article ID: KB0093409
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
Possible deadlock in the EMS Java client libraries.
Symptoms:
Java client application hangs.
Cause:
The following issues have been fixed in EMS 8.2:
EMS-5804
EMS-5857
Fixed a possible deadlock in the EMS Java client libraries. Situations where the client library could deadlock included when a connection was started, stopped or closed, and when a session was created. The risk of a deadlock was increased when the clock synchronization feature was used (clock_sync_interval defined in the server), or when messages had a JMSExpiration set.
Resolution
Sample thread dumps of the Java client application are attached. (Filenames: j_threads_1.txt, j_threads_2.txt, j_threads_3.txt). To confirm a deadlock, create a thread dump of the application and send the full dump to TIBCO Support. The current workaround is to disable clock_sync_interval.
Issue/Introduction
Possible deadlock in the EMS Java client libraries.
Additional Information
EMS 8.2 release note.
Feedback
Yes
No
Powered by
