Fixes are available
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When WebSphere Application Server default Messaging Provider, implemented by the Service Integration Bus (SIB), connects to a WebSphere MQ, the error 2025 (MQRC_MAX_CONNS_LIMIT_REACHED) is seen on the MQ side when the channel initiator is restarted. On the SIB side, the following are written to an FFDC file: at com.ibm.mq.MQQueueManagerFactory.processException(MQQueueMana gerFactory.java:959) at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQ ueueManagerFactory.java:880) at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueMa nagerFactory.java:171) at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:684)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * * Version 7.0, with WebSphere MQ Server bus * * members * **************************************************************** * PROBLEM DESCRIPTION: CWSIP0002 error with WebSphere MQ * * reason code 2025 * * (MQRC_MAX_CONNS_LIMIT_REACHED) * **************************************************************** * RECOMMENDATION: * **************************************************************** The service integration bus messaging engine incorrectly sets a limit on the number of internally created connections to the WebSphere MQ Server bus member queue manager. Under normal operation, this might cause MQRC_MAX_CONNS_LIMIT_REACHED exceptions, which are treated as severe exceptions by the messaging engine and cause MDB applications to be disconnected and need to reconnect to the bus. In addition, the incorrect specification of a limit by the messaging engine combines with WebSphere MQ APAR IZ83390, causing MQRC_MAX_CONNS_LIMIT_REACHED errors to be reported even when the limit has not been reached, especially after losing connectivity to a queue manager.
Problem conclusion
The fix for this APAR removes the incorrectly specified internal limit on the number of connections a messaging engine could make to a queue manager. This removes the possibility of encountering WebSphere MQ APAR IZ83390, and prevents the arbitrary limit from causing CWSIP0002 errors during normal operation. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM21994
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-06
Closed date
2010-10-29
Last modified date
2010-10-29
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
620800101
Applicable component levels
R300 PSY
UP
Document Information
Modified date:
24 October 2021