| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with Pub Sub JMS client |
« View previous topic :: View next topic » |
| Author |
Message
|
| amoljoshi |
 Posted: Fri Dec 31, 2004 1:44 am Post subject: Problem with Pub Sub JMS client |
 |
|
Newbie
Joined: 31 Dec 2004
Posts: 6
|
Hi,
We are currently in the process of evaluating the following combination for our production system.The software used was
# WAS5.1 Trial
# MQ 5.3 (MA0C patch for Pub Sub support).
After installing the Patch also have run the setup script MQJMS_
PSQ.mqsc and even confirmed that the broker for the APPServer Queue manager is running.
Have created the Topic connection factory and topics using WAS admin console.
Currently getting following errors
1. In app server log it says
[12/30/04 15:07:14:480 GMT+05:30] 3cf72199 JMSEmbeddedPr A MSGS0052I: Starting the Broker
[12/30/04 15:07:14:745 GMT+05:30] 3cf72199 BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[12/30/04 15:07:14:745 GMT+05:30] 3cf72199 JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
2. The JMS client dies with error
com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No broker response. Please ensure that the broker is running. ***
at com.ibm.mq.jms.MQTopicSession.getBrokerResponse(MQTopicSession.java:1835)
at com.ibm.mq.jms.MQTopicPublisher.checkBrokerResponse(MQTopicPublisher.java:1444)
at com.ibm.mq.jms.MQTopicPublisher.publish(MQTopicPublisher.java:533)
at com.ibm.mq.jms.MQTopicPublisher.publish(MQTopicPublisher.java:592)
at JMSTester.main(JMSTester.java:128)
Am i missing any steps here? |
|
| Back to top |
|
 |
| slaupster |
| Posted: Fri Dec 31, 2004 6:16 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2004
Posts: 41
|
it sounds like you've got your products confused and are trying to use external MQ and embedded MQ at the same time.
| Quote: |
[12/30/04 15:07:14:480 GMT+05:30] 3cf72199 JMSEmbeddedPr A MSGS0052I: Starting the Broker
[12/30/04 15:07:14:745 GMT+05:30] 3cf72199 BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[12/30/04 15:07:14:745 GMT+05:30] 3cf72199 JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085 |
The above quote is from your SystemOut.log and it shows WAS trying to start the embedded broker, but you are trying to use MQ pub/sub (ma0c). Basically, you want your own QMGR that you defined and ran the MQJMS_PSQ.masc file against to provide your JMS and not your embedded JMS server. If so, you should not have installed embedded messaging. At this point you can simply stop the JMSServer from being started when starting server1 by:
Application Servers -> server1 -> Server Components -> JMSServer -> change Initial State to "Stopped". After this the embedded JMS server will not attempt to start and you must do your JMS with the QMGR you have defined with ma0c in mind. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 31, 2004 11:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Why use MA0C ?
Get to MQ 5.3 CSD08 and you don't need the support pack.!
As for shutting down internal MQ it should not be necessary.
However the configuration in the management console must be right
Remove all your config under resources-- Webspher JMS
Set up all your config under resourcess -- Websphere MQ JMS
and make sure there is no naming (JNDI) conflict
Enjoy  |
|
| Back to top |
|
|
| amoljoshi |
| Posted: Sun Jan 02, 2005 8:32 pm Post subject: |
|
|
Newbie
Joined: 31 Dec 2004
Posts: 6
|
hi
thanks for the replies...
As specified , i am using WAS5.1 trial.Embedded messaging does not get installed for a trial version.
Since the sequence of installation was
1. WMQ
2. Patch(MA0C)
3. WAS5.1 trial
During WAS installation , it detected the MQ installation and created the Queue Manager and the queues.
And the script was run as specified in the guide for using MQSeries using Java.
I am sorry if I have missed anything.
In short,we want to achieve the following.
# Pub - Sub support with MQ5.3
# MDB based architecture on WAS5.1 trial.
So what should be the ideal steps?
I am not very sure wheather the CSD patch is still available or now...
thanks
Amol |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Jan 04, 2005 6:14 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I think that you want to do what slaupster mentioned above. Don't start your embedded server. This will keep it from attempting to come up which appears to be part of your problem. The other thing to do is to manually create a qmgr and have it and its MA0C broker running. You can then define your JMS resources as WebSphere MQ resources and you should be good to go. |
|
| 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
|
|
|
|
