| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mangesh1187 |
 Posted: Fri Nov 21, 2014 1:31 am Post subject: com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053 |
 |
|
Centurion
Joined: 23 Mar 2013
Posts: 116
|
This is regarding the pubsub setup I established. Following is the details:
MQ SERVER
MQ Version : 7.5.0.0
QUEUE MANAGER : QM1
PSMODE property : ENABLED
Client Application
JMS CLIENT
Since its JMS client I have created the required JMS queues in QM2 using , MQJMS_PSQ.mqsc file provided with MQ.
Scenario 1:
When we used the SimpleWMQJMSPubSub ( Without JNDI, provided in JMS sample folder) the client application was able to publish message on queue manger & able to successfuly subscibe.
I can see the notable differance here is we have not used any publiciation queue in the code.
Scenario 2:
But when we used JNDI , JmsJndiProducer ( with .binding file created using the MQ Explorer) the Client application was getting the below error:
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 ***
Inner exception(s):
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
FAILURE
I could see the PSMODE attribute is correcty set to ENABLED so that the queued publication can heppen. I can see messages are reaching to the publication queue i.e. TESTQ
Can you please guide me if I am missing something here .
Following is some of the content of .binding file used in Scenario 2 :
Connection Factory
Name : testCF
Messaging Provider : Websphere MQ
Type : Topic Connection Factory
Transport : MQClient
Properties
General
Name:testCF
Description:Tactical envrionment TCF
ClassName:MQTopicConnectionFactory
Messaging Provider : Websphere MQ
Transport:Client
Provider Version:6
Client Identifier:
CCSID : 819
Broker Sub Queue : SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
Broker cc Sub Queue : SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
Broker Control queue : SYSTEM.BROKER.CONTROL.QUEUE
Publication Stream : TESTQ
Broker Version : V2
Connection
Base Queue Manager:QM2
Broker
Queue Manager:QM2
Destination
General
Name :testDest
Topic : TOPIC1/TOPIC2 ( Name changed)
Extended
Target Client : JMS
(Other properties are default) |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Nov 21, 2014 2:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Please apply the 7.5.0.3 (or later fixpack)
Then
| Code: |
Inner exception(s):
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
FAILURE
|
confuses me. Are you trying to read a publicatino or what.
As an MQ error, 2033 means 'no messages'. Either the Queue is empty or there are no messages that match the criteria in your MQGET/BROWSE operation.
Please give us some detail about what you were really trying to do when you received this error
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 21, 2014 8:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| Quote: |
Publication Stream : TESTQ
|
This is plain wrong. It should be SYSTEM.BROKER.DEFAULT.STREAM
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
