| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| An MQException |
View previous topic :: View next topic |
| Author |
Message
|
| vijay_thatte |
 Posted: Mon Oct 18, 2004 9:04 pm Post subject: An MQException |
 |
|
Newbie
Joined: 18 Oct 2004
Posts: 2
|
We have the following problem in production which occurs when we try to create an object using MQQueueManager mq=new (MQQueueManger(“”);
The error trace is as below.
Exception caught:com.ibm.mq.MQException: 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:239)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConection(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:737)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:400)
at IbsrmMQclient.<init>(IbsrmMQclient.java:119)
at IbsrmCheck.ibsrm_status_ok(IbsrmCheck.java:112)
at IbsrmCheck.start(IbsrmCheck.java:89)
at IbsrmCheck.main(IbsrmCheck.java:190)
Please note that we are not using the JMS to connect to MQ Manager. Also regarding the Manager, Queue, and channel etc, it is already confirmed that those are fine and running on server.
The application was able to connect before it was upgraded to MQ 5.3 from 2.21. The server setup is on Mainframe.
So is it a problem due to version upgradation?
Also when written a very simple client to connect to mq server (mainframe) it is giving the following error below.
The same code is working fine with the dummy mqseries setup(all objects with the same name but different machine IP) on the local server (unix).
Error:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for ''
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1775)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1168)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
at GGATestClient.main(GGATestClient.java:175)
hemant 123...MQJMS2005: failed to create MQQueueManager for ''
Starting the Connection
java.lang.NullPointerException
at GGATestClient.main(GGATestClient.java:188)
Hemant: Caught exception: java.lang.NullPointerException
Greately appreciate any pointers and help in this regard at the earliest, |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Oct 19, 2004 5:42 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I'm guessing that your client attach feature needs to be upgraded as well. A mainframe expert can probably speak more definitively on this. My other guess would be that you don't have your listener running or you are attempting to connect to a default queue manager and you don't have one. |
|
| Back to top |
|
|
| vijay_thatte |
| Posted: Thu Oct 21, 2004 12:00 am Post subject: MQ mainframe connection Exception - CFA |
|
|
Newbie
Joined: 18 Oct 2004
Posts: 2
|
The issue is resolved by enabling/installing CFA (Client Feature Attachment). Thanks lot.
Please find mentioned below the methods to check if the Client Attachment Feature is available/enabled
1) Use the FM ID of the CSI repository.
On the WebSphere MQ for OS/390 Program Directory, find the FM ID of the optional MQ Client Attach feature.
Use this FM ID, and query the SMP/E CSI repository to determine the status of the FM ID.
2) Examining the MVS SDSF log when the WebSphere MQ MSTR address is coming up.
Look for the WebSphere MQ message:
+CSQX099I %CSQ1 CSQXGIP Client attachment feature available |
|
| 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
|
|
|
|
