PK84308: WebSphere MQ messaging provider JMS Topic objects do not delegate the Broker publication queue to the JMS Connection

Fixes are available

APAR status

Closed as program error.

Error description

JMS Topic objects defined in the WebSphere MQ messaging
provider should delegate the "Broker publication queue"
property to the connection factory.
However, the default value is used regardless of the setting
on the connection factory.
com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No
broker response. Please ensure that the broker is running. If
you are us ing the WebSphere MQ broker check that your
brokerVersion is set to V1 ***

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Version 7.0 using WebSphere MQ as a         *
*                  messaging provider                          *
****************************************************************
* PROBLEM DESCRIPTION: When the "Broker publication queue"     *
*                      (brokerPubQueue) property of a          *
*                      Topic is set to "As connection" the     *
*                      wrong value is used                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the "Broker publication queue" property of a JMS Topic in
the WebSphere MQ messaging provider is set to "As connection",
the value used at runtime should be inherited from the
connection factory (or topic connection factory) used by the
application to connect to WebSphere MQ.

However, the default value of "SYSTEM.BROKER.DEFAULT.STREAM"
is used regardless of what value has been specified in the
connection factory.

This is likely to result in the following exception
being thrown when an application attempts to publish a message:

com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No
broker response. Please ensure that the broker is running. If
you are using the WebSphere MQ broker check that your
brokerVersion is set to V1 ***
at com.ibm.msg.client.wmq.v6.jms.internal.MQPubSubServices.
                    getBrokerResponse(MQPubSubServices.java:565)
at com.ibm.msg.client.wmq.v6.jms.internal.JMSServicesMgr.
                      getBrokerResponse(JMSServicesMgr.java:297)
at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.
                checkBrokerResponse(MQMessageProducer.java:2524)
at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.
                         publishInt(MQMessageProducer.java:1621)
at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.
                                send(MQMessageProducer.java:733)
at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.
                               send(MQMessageProducer.java:2725)
at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.
                    sendMessage(JmsMessageProducerImpl.java:884)
at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.
                          send_(JmsMessageProducerImpl.java:739)
at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.
                           send(JmsMessageProducerImpl.java:398)
at com.ibm.mq.jms.MQMessageProducer.
                                send(MQMessageProducer.java:281)
at com.ibm.ejs.jms.JMSMessageProducerHandle.
                        send(JMSMessageProducerHandle.java:1182)
...

Problem conclusion

The fix for this APAR ensures that the broker publication
queue specified on the connection factory is used at runtime,
when the "Broker publication queue" property of the topic is
set to "As connection".

This APAR is targeted for delivery in WebSphere Application
Server Fix Pack 7.0.0.5.

Temporary fix

Comments

APAR Information

APAR number
PK84308
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
2009-04-08
Closed date
2009-06-29
Last modified date
2009-06-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

PK84308: WebSphere MQ messaging provider JMS Topic objects do not delegate the Broker publication queue to the JMS Connection

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?