| Author |
Message
|
| susilkp |
 Posted: Tue Apr 13, 2004 11:35 am Post subject: Broker Manager unable to attach to Queue Manager - unknown Q |
 |
|
Newbie
Joined: 13 Apr 2004
Posts: 5
|
I am running WSAD 5.1 with embedded messaging. When I start the server, the Queue manager starts up, but the broker manager does not. Here is the error I get.
[4/13/04 14:23:33:469 EDT] 4e7288e0 JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[4/13/04 14:23:43:469 EDT] 4e7288e0 JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
[4/13/04 14:23:43:484 EDT] 4e7288e0 JMSEmbeddedPr A MSGS0052I: Starting the Broker
[4/13/04 14:23:43:719 EDT] 4e7288e0 SystemErr R MQJE001: Completion Code 2, Reason 2085
[4/13/04 14:23:43:750 EDT] 4e7288e0 BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[4/13/04 14:23:43:828 EDT] 4e7288e0 JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
at com.ibm.ws.messaging.BrokerManager.attachToMQ(BrokerManager.java:439)
at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:234)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Any suggestions?
Thanks |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue Apr 13, 2004 11:54 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
2085 is unknown_q_name. Check to see if the queue you are trying to open is actually present and that you spelled it right. Nothing to do with queue manager not starting up. If that were to be the case you would have gotten 2058/2059.
Cheers
Kumar |
|
| Back to top |
|
|
| susilkp |
| Posted: Tue Apr 13, 2004 12:27 pm Post subject: |
|
|
Newbie
Joined: 13 Apr 2004
Posts: 5
|
I do not have a clue which queue the broker manager is looking for.
How to find that out? |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Apr 13, 2004 1:12 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
If you cannot look up the code where a call to accessQueue is being made. Then the other alternative would be to check the docs for the setup of your broker and its environemnt. Very much possible that you missed out a few steps that needed some queues to be defined.
Cheers
Kumar |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Apr 13, 2004 1:16 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| My guess would be that you need to run the MQJMS_PSQ.mqsc through runmqsc against your queue manager. However, I would have expected this to be done if you are using an embedded JMS qmgr. |
|
| Back to top |
|
|
| susilkp |
| Posted: Wed Apr 14, 2004 6:58 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2004
Posts: 5
|
I have the following queues in the queue manager. So running MQJMS_PSQ.mqsc is not going to do anything extra. Any other suggestions?
display queue(*)
1 : display queue(*)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.BROKER.DEFAULT.STREAM) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CHANNEL.INITQ) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.REPOSITORY.QUEUE)
TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEAD.LETTER.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.ALIAS.QUEUE) TYPE(QALIAS)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.LOCAL.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.MODEL.QUEUE) TYPE(QMODEL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.REMOTE.QUEUE) TYPE(QREMOTE)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.ADMIN.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE)
TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.D.SUBSCRIBER.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.MODEL.QUEUE) TYPE(QMODEL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE)
TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.ND.SUBSCRIBER.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.PS.STATUS.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.JMS.REPORT.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.MQSC.REPLY.QUEUE) TYPE(QMODEL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.PENDING.DATA.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(WAS.BROKER.EXECUTIONGROUP.REPLY)
TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(WAS.PCF.REPLY) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(WQ_SYSTEM.DEFAULT.LOCAL.QUEUE) TYPE(QLOCAL) |
|
| Back to top |
|
|
| susilkp |
| Posted: Wed Apr 14, 2004 9:57 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2004
Posts: 5
|
I could not find what queue name the broker manager is looking for. I even looked at the resource xml files.
There is nothing in the documentation to set-up the broker manager.
If I search for "Borker Manager" in the help, I get only one entry for Message reference. There are a couple of entries only for messages. One of the messages is what I am getting. Here it is.
| Code: |
MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
Explanation: The JMS Server could not connect to the internal WebSphere MQ Queue Manager because a required queue does not exist. The JMS Server will not be usable for publish/subscribe.
User Response: Check the createmq.log file in the logs directory. Check the WebSphere MQ Queue Manager error logs.
|
But there is no createmq.log file in the logs directory or anywhere else in the file system. There is nothing in the Q manager error logs to explain this.
Any idea?
Thanks. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed Apr 14, 2004 10:09 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
If you have a way to run this app/broker in debug so as to give you more clues, then do so. It may show the queue name it is missing. Alternatively you could run a trace which too might show the queue name it is trying to open.
If there isnt any script file that is supplied to you for objects(queue) creation, then there must be some writeup someplace in the QB/readmes/manuals to say which queues need to be defined and on which queue manager. It is impossible that this information is missing from any of these, if this info is needed by the broker.
Cheers
Kumar |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Apr 14, 2004 10:10 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You could try running an MQ Trace when you try and connect. You can then search for the 2085, and look at the Control Blocks to see what Queue it is trying to Open.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| susilkp |
| Posted: Thu Apr 15, 2004 1:26 pm Post subject: |
|
|
Newbie
Joined: 13 Apr 2004
Posts: 5
|
I was unable to resolve this with all the suggestion I got here. But thanks to all of you.
I went ahead using JMS Point to Point where the broker manager is not required. If I find any solution, I will post it here.
Thanks again. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Thu Apr 15, 2004 4:58 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Glad to know that you got a workaround. But when you say " was unable to resolve this with all the suggestion I got here." do you mean you tried all of these.
-Run trace
-Read all the manuals to see if any mandatory queue was missing.
-Verify the code, if possible.
-Any other means to see if a queue was missing, like comparing your setup with any other that is successfully run.
If you have done all of the above and still did not get any answers, then i would highly doubt you would ever get a solution to this. Because there isn't anything beyond that one could do. :)
But do post your findings, would surely help others in their investigations.
Cheers
Kumar |
|
| Back to top |
|
|
|
|
