PK70904: WEBSPHERE MQ QUEUES CREATED USING THE ADMINISTRATIVE CONSOLE HAVE A DEFAULT QUEUE MANAGER PORT OF 0 INSTEAD OF NULL.

Fixes are available

APAR status

Closed as program error.

Error description

When a WebSphere MQ Queue is created, by default a
value of "0" is populated in the queue manager port field in the
administrative console. The field should be empty, null, by
default.
   According to the WebSphere AppServer v6.1 Information Center
the default value should be null not 0.
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?
topic=/
com.ibm.websphere.nd.doc/info/ae/ae/umj_pqdsm.html
.
   This shows the default value that is set for the
queueManagerPort.
<factories xmi:type="resources.jms.mqseries:MQQueue"
xmi:id="MQQueue_1173768881375"
name="IBM.QUEUE.101"
jndiName="JMS/QUEUE/IBMQUEUE"
persistence="APPLICATION_DEFINED"
priority="APPLICATION_DEFINED"
specifiedPriority="0" expiry="APPLICATION_DEFINED"
specifiedExpiry="0"
baseQueueName="IBM.QUEUE.101" baseQueueManagerName="IBM30J"
useNativeEncoding="false" integerEncoding="Normal"
decimalEncoding="Normal"
floatingPointEncoding="IEEENormal" targetClient="JMS"
queueManagerPort="0"/>

Local fix

If the value "0" is removed from the admin console then a
blank is stored for the port in resources.xml. If a blank value
is passed then by default "1414" is considered. But if the
value is stored as "0" then port "0" is used for connection.
.
   You can use the WebSphere Administrative Console to set the
value to blank.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server V6.1  *
*                  and 7.0 using WebSphere MQ as a messaging   *
*                  provider.                                   *
****************************************************************
* PROBLEM DESCRIPTION: When a WebSphere MQ JMS connection      *
*                      factory or queue is created in          *
*                      WebSphere Application Server V6.1       *
*                      using the administrative console the    *
*                      queue manager port is populated with    *
*                      a "0".  When the resource is saved      *
*                      this means that a "0" is saved in the   *
*                      configuration for that resource.  The   *
*                      information center states that this     *
*                      setting defaults to Null (empty).       *
*                                                              *
*                      When a WebSphere MQ JMS queue is        *
*                      created in WebSphere Application        *
*                      Server V7.0 using the administrative    *
*                      console the queue manager port is       *
*                      populated with a "0" in the MQ Queue    *
*                      Connection Properties panel. When the   *
*                      resource is saved this means that a     *
*                      "0" is saved in the configuration for   *
*                      that resource.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is not a functional problem in WebSphere Application
Server V6.1 because if the queue manager port is set to 0
WebSphere Application Server attempts to use port 1414 to
connect to WebSphere MQ.

However in V7.0 WebSphere Application Server attempts to use
port 0 if that was the value specified in the queue manager
port field of the MQ Queue Connection Properties panel when it
was saved.

Problem conclusion

This APAR corrects the default queue manager port field for
WebSphere MQ JMS connection factories and queues.

In WebSphere Application Server V6.1 the default value for the
fields on the connection factory and queue panels has been
changed to empty (null), as specified in the documentation.
At runtime the code will default to port 1414.

In WebSphere Application Server V7.0 the default value for the
field on the queue panel has been changed to 1414.
Connection factories are not affected by this APAR in V7.0
because they already correctly initialized the field to 1414.

The fix for this APAR is currently targeted for inclusion in
fixpack 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

Comments

APAR Information

APAR number
PK70904
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-08-21
Closed date
2008-11-25
Last modified date
2009-04-03

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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:
29 December 2021

Tips

PK70904: WEBSPHERE MQ QUEUES CREATED USING THE ADMINISTRATIVE CONSOLE HAVE A DEFAULT QUEUE MANAGER PORT OF 0 INSTEAD OF NULL.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?