PK78532: INCORRECT POOLING USED FOR WSADMIN-CREATED MQQUEUECONNECTIONFACTORY

Fixes are available

APAR status

Closed as program error.

Error description

When an MQQueueConnectionFactory is created in the wsadmin
scripting environment using 'AdminConfig.create()' rather than
'AdminConfig.createFromTemplate()', the administrative console
will show a "Maximum connections" value of 10 for the session
pool.  However, at runtime the application server will use a
maximum connections value of 0 (unlimited) instead.

Local fix

Connection factories created through the WebSphere Application
Server administrative console or using any of the templates
supplied with AdminConfig.createFromTemplate() are not affected.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  WebSphere Application Server V6.1 and V7.0  *
****************************************************************
* PROBLEM DESCRIPTION: When an MQQueueConnectionFactory is     *
*                      created in the wsadmin                  *
*                      scripting environment using             *
*                      'AdminConfig.create()' rather than      *
*                      'AdminConfig.createFromTemplate()',     *
*                      the administrative console              *
*                      shows a "Maximum connections"           *
*                      value of 10 for the session             *
*                      pool.  However, at runtime the          *
*                      application server will use a           *
*                      maximum connections value of 0          *
*                      (unlimited) instead.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem only affects WebSphere MQ connection factories
created using the create method of AdminConfig, where the
sessionPool attribute was not specified (this is not a
required attribute).

Connection factories created using the administrative console,
or any of the templates supplied for use with the
createFromTemplate method of AdminConfig, are not affected.

The existence of the sessionPool attribute in the
MQQueueConnectionFactory configuration object, even without
the maxConnections attribute specified, prevents this issue
from occurring.

Problem conclusion

The fix for this APAR changes the runtime value used for
maxSessions to 10, when the sessionPool attribute of the
MQQueueConnectionFactory configuration object is not specified.
This matches the value shown in the administrative
console when the connection factory is viewed.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.5.  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
PK78532
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
2009-01-13
Closed date
2009-02-24
Last modified date
2009-06-18

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

PK78532: INCORRECT POOLING USED FOR WSADMIN-CREATED MQQUEUECONNECTIONFACTORY

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?