Message Queue

This section describes known Java message queue issues and associated solutions.

JMS Reconnection Not Successfully Completed in Timing-Dependent Cases(IDs 6173308, 6189645, 6198481, 6199510, 6208728)

Failures to reconnect in timing-dependent scenarios can be caused by several problems.

Solution

You can work around these problems by:

• Restarting the brokers involved

• Restarting the Application Server instances involved

Asynchronous Message Listener Behavior Changed in appclient From 8.0 to 8.1 Update 2 (ID 6198465)

Due to a recent change, when an asynchronous message listener is the only live thread in the app-client container, the remaining appclient virtual machine exists as a daemon. This behavior is a regression for older applications that perform asynchronous receives in ACC. This problem affects application clients that set a JMS message listener and exit the main thread.

Solution

Do not exit the main thread. Wait for the message listener to notify the main thread before terminating the main thread.