| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Reason 2059 |
« View previous topic :: View next topic » |
| Author |
Message
|
| dhanunjay |
 Posted: Fri May 21, 2004 6:12 am Post subject: Reason 2059 |
 |
|
Newbie
Joined: 18 May 2004
Posts: 8
Location: Birmingham, AL
|
qmanager and listener is up and running. can anyone speculate what the reason for this error might be??
Thanks
<May 20, 2004 2:01:12 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: Customer/DataPublis
hV1_L_InternalMDBV1_1 is unable to connect to the JMS destination: ANY.CDPL.V1. The Error was:
[EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The error was:
[EJB:010196]'javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'msgqr1a.xxx.xxx.com:msgqr
1a'' Linked exception = 'com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2
059
MQJE011: Socket connection attempt refused'.
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'msgqr1a.xxx.xxx.com:msgqr1a'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1736) |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri May 21, 2004 6:30 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I saw your other post. You could have gotten away with the single post here rather than two posts.
A 2059 is queue manager unavailable. Based on the name of your qmgr, I'm guessing that you are using the full MQ product and not embedded JMS. My guess would be that you don't have the listener running for the queue manager or you specified some incorrect values on your QCF/TCF definition. |
|
| Back to top |
|
|
| dhanunjay |
| Posted: Fri May 21, 2004 7:21 am Post subject: |
|
|
Newbie
Joined: 18 May 2004
Posts: 8
Location: Birmingham, AL
|
| bower5932 wrote: |
I saw your other post. You could have gotten away with the single post here rather than two posts.
A 2059 is queue manager unavailable. Based on the name of your qmgr, I'm guessing that you are using the full MQ product and not embedded JMS. My guess would be that you don't have the listener running for the queue manager or you specified some incorrect values on your QCF/TCF definition. |
posting messages in two forums was accidental. i wanted to post it in the other forum.
abt the question, the qmanager and listener were up and workin for a long time (5-6 months). one of the situations i saw this reason code was when our pubsub framework..opened up a lot of channels and clogged the qmanager. this time..it doesnt seem to be the problem.
can you suggest where i could look or do to check where the problem might be?? |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri May 21, 2004 8:41 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| If you are sure that your qmgr/listener are running, you could try the netstat -a command to see if there are a lot of tcp sessions in use. You could also check the amqerrxx logs to see if there is something in them. You could also check your QCF/TCF definition to make sure that everything is specified correctly. |
|
| 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
|
|
|
|
