PK72627: Problems seen with WebSphere MQ Server members of a service integration bus.

Fixes are available

APAR status

Closed as program error.

Error description

Problems seen when destinations within a service integration
bus are hosted on WebSphere MQ queue managers, configured as
WebSphere MQ Server members of the bus.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server 7.0   *
*                  with WebSphere MQ Server members of a       *
*                  service integration bus.                    *
****************************************************************
* PROBLEM DESCRIPTION: Buildup of connections from WebSphere   *
*                      Application Server to WebSphere MQ,     *
*                      or OutOfMemoryErrors, when using        *
*                      WebSphere MQ Server bus members.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When sending and/or receiving messages with a queue manager
which is a member of the bus, where WebSphere Application
Server and the WebSphere MQ queue manager are on the same z/OS
machine and WebSphere Application Server is connected to the
queue manager in bindings mode, it may not be possible to send
or receive any more messages after a period of time. This is
because the internal connections used by WebSphere Application
Server to connect to WebSphere MQ are not being closed after
use, so the limit on the maximum number of connections to the
queue manager is quickly reached.  At this point an error
message containing MQRC 2025 - MQRC_MAX_CONNS_LIMIT_REACHED is
generated.

When using an MDB that uses a secure connection to consume
messages from an MQ Server bus member it is possible to
experience an OutOfMemoryError on the server that the MDB is
running on. Analysis of a heapdump for the server  will show a
large number of
MQClientManagedConnectionFactoryJ11/com.ibm.websphere.ssl.protoc
ol.SSLSocketFactory objects.

Problem conclusion

```
This APAR fixes these problems.
```

Temporary fix

Comments

APAR Information

APAR number
PK72627
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
2008-09-23
Closed date
2008-11-14
Last modified date
2008-11-14

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:
23 October 2021

Tips

PK72627: Problems seen with WebSphere MQ Server members of a service integration bus.

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?