PM21994: WHEN SERVICE INTEGRATION BUS CONNECTS TO MQ, ERROR 2025 (MQRC_MA X_CONNS_LIMIT_REACHED) OCCURS UPON RESTARTING CHANNEL INITIATOR.

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM21994: WHEN SERVICE INTEGRATION BUS CONNECTS TO MQ, ERROR 2025 (MQRC_MA X_CONNS_LIMIT_REACHED) OCCURS UPON RESTARTING CHANNEL INITIATOR.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R300 PSY

Document Information

Share your feedback

Need support?