| Author |
Message
|
| kavithadhevi |
 Posted: Fri Mar 05, 2004 6:25 am Post subject: No broker response with 3023 error |
 |
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
My environment is MQ 5.3 on Windows W2K support pac CSD04.
I am getting this error "NoBrokerResponseException: MQJMS5053: *** No broker response". Please ensure that the broker is running. " and the odd thing is broker is running and the message format is set to MQHRF2. I restarted the queue manager and broker still the same.... 
I was not able to find a solution from the post here.
Any thoughts??? 
_________________
Thanks in Advance. 
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Mar 05, 2004 6:29 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I've seen problems like this (with MA0C) when there is a 'bad message' on one of the broker queues. I'd suggest shutting down the broker and checking out what messages are on its queues. It might shed some light on what is wrong. |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Mon Mar 08, 2004 9:56 am Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
Good idea. I will scrutanize messages in DEAD Letter queue.
How do i get the broker run without throwing this error mean while?
I tried queue manager restart too..
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 08, 2004 10:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, it's not the DEAD letter queue you should probably look at, if I understand bower5932's post.
It's the SYSTEM.BROKER.* queues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Balmer |
| Posted: Mon Mar 08, 2004 10:16 am Post subject: |
|
|
Novice
Joined: 19 Jun 2003
Posts: 13
|
Please check all the causes below...
MQJMS5053 *** No broker response. Please ensure that the broker is running. ***
Explanation: Possible causes:
Broker is not running.
You are using BrokerVersion=V2 in your TopicConnectionFactory with the MQSeries Publish/Subscribe broker, which does not support this.
The Broker has rejected the Publication or Subscription and placed it on the SYSTEM.DEAD.LETTER.QUEUE
User Response: Ensure that your broker is running. Check the system event log for broker error messages. Check that the broker supports the BrokerVersion you are using. Check the SYSTEM.DEAD.LETTER.QUEUE for rejected messages.
Apart from the above,
1. are u connecting as a JMS client ?
if so, make sure that channel listener is running and u specified the right port no in TCF as well as QCF whatever u r using ?
2. how did u create stream queues ?
If u r using stream queues, can u provide us the stream queue properties ?
3. Make sure that all the JMS queue exist when u connect as a client as there will be JMS queues names in context properties ?
thanks
Balmer |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Wed Mar 10, 2004 1:26 pm Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
I checked for the broker version in the Websphere. Its set to Basic - which means it uses MA0C.
Listener and everything is running just fine. Only part which is affected is JMS part where i am not able to subscribe, which lands up in the dead letter queue.
From the JMS Client side, they haven't changed anything in regards to the JMS message format verion.
Any thoughts?
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 10, 2004 2:02 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you shut down the broker, and then scrutinize the messages in the SYSTEM.BROKER.* queues?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Mar 10, 2004 3:28 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I just ran into a similar type of problem on this today. I was publishing on one stream queue and subscribing on another. My subscriber wasn't picking up any of the publishes. I'm not sure if this is your problem, but I thought I would pass it along. |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Mon Mar 15, 2004 10:18 am Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
No that would be the one cos client application doesn't use any option. So everything uses default ...
They use SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE.
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
|
|
