Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2.GA
-
Fix Version/s: 1.8.2.GA
-
Component/s: Enterprise Push Server
-
Labels:None
-
Environment:JMS
Description
In certain circumstances, the DefaultMessageService attempts to reconnect to JMS in order to support failover. However, when applications using the DefaultMessageService (either eps.war or an application.war) are in the midst of being shut down knowningly and gracefully, the attempts to reconnect can lead to various exceptions (e.g ClassNotFound).
It's recommended that the service listen for and respond to contextDestroyed events so that the reconnection logic can be shut down.
It's recommended that the service listen for and respond to contextDestroyed events so that the reconnection logic can be shut down.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Assigning to Greg for verification and closure. I know that we've checked in the code for this and that it solved some of the issues that we were seeing. Additional thread cleanup issues should get their own specific JIRA.
Show
Deryk Sinotte
added a comment - Assigning to Greg for verification and closure. I know that we've checked in the code for this and that it solved some of the issues that we were seeing. Additional thread cleanup issues should get their own specific JIRA.
The code no longer attempts to reconnect when the servlet container is shut down in Tomcat and WebSphere.