| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJE011: Socket connection attempt refused |
« View previous topic :: View next topic » |
| Author |
Message
|
| satya_jammy |
 Posted: Sat Oct 17, 2009 1:21 am Post subject: MQJE011: Socket connection attempt refused |
 |
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
Hi Gurus,
One of my client App unable to connect to the QManager . The app is generaing the error
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
2059 means Qmanager unavailable. But the Qmanager is running fine and all the other apps are connected Successfully. Why only this app is unable to connnect to QM.? This an old application and able to do transactions with QM till today. it is failing Now only.. What factors i need to check from QM side? here is the complete error that the client app is generating.
Beginning of readMQQueue() ...
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:242)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:276)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:296)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:754)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:688)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:469)
at com.avaya.srd.arch.mq.MQReader.readMQQueue(MQReader.java:215)
at com.avaya.srd.arch.mq.MQDriver.main(MQDriver.java:61)
Caused by: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQInternalCommunications.createSocketConnection(MQInternalCommunications.java:1690)
at com.ibm.mq.MQInternalCommunications.access$000(MQInternalCommunications.java:114)
at com.ibm.mq.MQInternalCommunications$1.run(MQInternalCommunications.java:505)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.mq.MQInternalCommunications.<init>(MQInternalCommunications.java:501)
at com.ibm.mq.MQSESSIONClient.MQCONN(MQSESSIONClient.java:1344)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:218)
... 9 more
java.lang.NullPointerException
at com.avaya.srd.arch.mq.MQReader.readMQQueue(MQReader.java:235)
at com.avaya.srd.arch.mq.MQDriver.main(MQDriver.java:61)
Beginning of readMQQueue() ...
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:242)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:276)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:296)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:754)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:688)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:469)
at com.avaya.srd.arch.mq.MQReader.readMQQueue(MQReader.java:215)
at com.avaya.srd.arch.mq.MQDriver.main(MQDriver.java:61)
Caused by: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQInternalCommunications.createSocketConnection(MQInternalCommunications.java:1690)
at com.ibm.mq.MQInternalCommunications.access$000(MQInternalCommunications.java:114)
at com.ibm.mq.MQInternalCommunications$1.run(MQInternalCommunications.java:505)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.mq.MQInternalCommunications.<init>(MQInternalCommunications.java:501)
at com.ibm.mq.MQSESSIONClient.MQCONN(MQSESSIONClient.java:1344)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:218)
... 9 more
java.lang.NullPointerException
at com.avaya.srd.arch.mq.MQReader.readMQQueue(MQReader.java:235)
at com.avaya.srd.arch.mq.MQDriver.main(MQDriver.java:61)
Beginning of readMQQueue() ...
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused |
|
| Back to top |
|
 |
| exerk |
| Posted: Sat Oct 17, 2009 2:20 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What changed? Was maintenance applied to WMQ? Changes to the server, firewalls, etc.?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| satya_jammy |
| Posted: Sat Oct 17, 2009 3:53 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
OK The issue is resolved...
For interested people
As the issue is with only one app and the QM is available and other apps able to connect to it.. i strongly stood on my words that there is no issue with QM. I asked the Client person to do a telnet to the MQ listening port 1414 from the application running server . when he tried it failed to connect using telnet.. we contacted Firewall people and they fixed the connectivity issue  |
|
| 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
|
|
|
|
