Fixes are available
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Messages sent to a destination take a very long time to arrive when low volumes of messages are sent. The delay is variable and messages that are delayed will only be delivered when further messages are sent. Environments with this problem will see the following message in the SystemOut log any time before the observation of delayed messages: CWSIP0002E: An internal messaging error occurred in com.ibm.ws.sib.processor.utils.am.MPAlarmThread, <some exception>
Local fix
fix required
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * WebSphere Application Server Version 6.1 * **************************************************************** * PROBLEM DESCRIPTION: An unexpected error occurs within * * the messaging engine causing * * an important thread to terminate. * * The termination of this thread * * prevents correct operation of the * * messaging engine, and can delay the * * delivery of messages. * **************************************************************** * RECOMMENDATION: * **************************************************************** The thread that terminates after the unexpected error occurs is the message processor alarm manager. The exception is thrown from within a task being processed by the alarm manager thread. Because the exception is not caught, the thread is terminated. APAR PK76306 addresses one specific misconfiguration that can cause an exception of this type to be thrown.
Problem conclusion
This APAR changes the handling of exceptions by the alarm manager thread. This minimizes the risk of a runtime exception causing this thread to terminate. This APAR does not address the cause of any runtime exceptions. The cause of each runtime exception caught by the alarm manager thread must be investigated individually. When this APAR is applied, runtime exceptions thrown to the alarm manager thread are reported via an FFDC from one of the following classes: com.ibm.ws.sib.processor.utils.am.BachedTimeoutManager com.ibm.ws.sib.processor.utils.am.MPAlarmManager CWSIP0002E error messages are also reported in the JVM logs of the application server that is hosting the messaging engine. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK77354
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-11
Closed date
2008-12-30
Last modified date
2008-12-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
PLAT MSG COM
Fixed component ID
620600101
Applicable component levels
R200 PSY
UP
Document Information
Modified date:
28 December 2021