PK71746: Channels to WMQ not closed after MQ Config update.

Fixes are available

APAR status

Closed as program error.

Error description

If you use the administrative console MQ Config tool to create
or modify a WebSphere MQ queue the communication channel used
to modify the WebSphere MQ configuration is not closed.

Local fix

The connection that the MQ Config functionality in WSAS
establishes to do its work does not get closed.  After the work
has been completed make sure the connection does get cleaned
up.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server v6.1  *
*                  and v7 with WebSphere MQ as the JMS         *
*                  provider.                                   *
****************************************************************
* PROBLEM DESCRIPTION: Channels to WebSphere MQ (for example   *
*                      SYSTEM.DEF.SRVCONN) are created when    *
*                      the MQ Config functionality in          *
*                      WebSphere Application Server is used    *
*                      to create or modify a local queue on    *
*                      a WebSphere MQ queue manager. These     *
*                      channels are not closed after use and   *
*                      are not reused.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The MQ Config panel can be accessed by clicking on the link on
the WebSphere MQ Queue details panel in the administrative
console. It allows users to create or modify local queues
on a WebSphere MQ queue manager.

This opens a channel to the WebSphere MQ queue manager,
by default this is a SYSTEM.DEF.SVRCONN channel.

However, channels are not closed after the update is
submitted and they can accumulate.

Problem conclusion

This fix closes the channel to WebSphere MQ after a
configuration update.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.0.0.3.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Restarting the WMQ Server will release the resources

Comments

APAR Information

APAR number
PK71746
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-09-09
Closed date
2008-10-14
Last modified date
2008-10-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
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK71746: Channels to WMQ not closed after MQ Config update.

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

R200 PSY

Document Information

Share your feedback

Need support?