| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| what can cause such an error ??? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Al Pacino |
 Posted: Wed Aug 31, 2005 10:17 am Post subject: what can cause such an error ??? |
 |
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Like this one to happen
Throwable javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:queuemanger'
MQ 5.3
Windows NT
CSD 10
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Aug 31, 2005 10:26 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Lots of things.  Capture the "linked exception" to get the MQ Reason Code which will identify the error.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Aug 31, 2005 10:33 am Post subject: Re: what can cause such an error ??? |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| Al Pacino wrote: |
Like this one to happen
Throwable javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:queuemanger'
MQ 5.3
Windows NT
CSD 10 |
If the MQManager and the listener process running, you have a SVRCONN Channel defined on it as well as the appropriate Queue Objects then this is usually a problem with the JMS/QCF or JMS/Q definitions.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Wed Aug 31, 2005 12:31 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Eddie,
The linked exception is shown below:
Linked Exception: com.ibm.mq.MQException: Completion Code 2, Reason 2059
Csmith,
I am not seeing any issue with the the JMS/QCF or JMS/Q definitions.
I have to mention , I am an admin and trying to troubleshoot the issue with the developer 
thanks
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Wed Aug 31, 2005 12:49 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| Well, friend, there's this lovely-lovely-button floating about the upper right corner of your screen entitled "Search" - it is the most wonderful button in the world, it is your friend in need, your loving mistress on those cold cold WMQ nights, use it for "2059", don't be shy! |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Aug 31, 2005 1:02 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
From the WMQ Messages Guide.
| Code: |
2059 X’080B’ MQRC_Q_MGR_NOT_AVAILABLE
On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection.
v On z/OS:
– For batch applications, this reason can be returned to applications running in non-WebSphere MQ LPARs.
– For CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available.
v On OS/400, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in compatibility mode.
This reason code can also occur if a WebSphere MQ client application attempts to connect to a queue manager within a WebSphere MQ client queue-manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call).
This reason code can also occur if the call is issued by a WebSphere MQ client application and there is an error with the client-connection or the corresponding server-connection channel definitions. On z/OS, this reason code can also occur if the optional OS/390® client attachment feature has not been installed.
Corrective action: Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions. |
If the QManager is running and the channels are properly defined make sure the runmqlsr process is running and listening on the port you are trying to connect to. Also make sure the runmqchi process is running.
Then verify your JMS Connection settings.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| 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
|
|
|
|
