| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMSWMQ0018: Failed to connect to queue manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| mongo380 |
 Posted: Tue Mar 30, 2010 5:49 am Post subject: JMSWMQ0018: Failed to connect to queue manager |
 |
|
Newbie
Joined: 30 Mar 2010
Posts: 2
|
Hello
I am running a Q manager on a Vista box I have a Java JMS client program that reads messages from the Q The client connects and consumes messages when running locally (same PC as MQ), but when I try to run the client from another windows or solaris box on the network, I get connection failures
I am able to ping and telnet (host 1414) to the machine running the Q manager from either of the client boxes
When I start the client I receive a series of stack traces (see below)
I have seen numerous posts with similar issues, but none seem to solve the problem
Is there anything I need to configure on the Q manager to allow these incoming connections? Any other suggestions or things to check???
Please help
BTW, the client is connecting using client mode (1) and the channel is: SYSTEM DEF SVRCONN
Thanks in advance
Here is the stack trace:
| Code: |
Failed to connect to queue manager 'QM_L55' with connection mode 'Client' and host name 'ipaddress' ; nested exception is com ibm mq MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2059' ('MQRC_Q_MGR_NOT_AVAILABLE')
com ibm msg client jms DetailedIllegalStateException: JMSWMQ0018: Failed to connect to queue manager 'QM_L55' with connection mode 'Client' and host name 'ipaddress' Check the queue manager is started and if running in client mode, check there is a listener running Please see the linked exception for more information
at com ibm msg client wmq common internal Reason reasonToException(Reason java:496)
at com ibm msg client wmq common internal Reason createException(Reason java:236)
at com ibm msg client wmq internal WMQConnection <init>(WMQConnection java:421)
at com ibm msg client wmq factories WMQConnectionFactory createV7ProviderConnection(WMQConnectionFactory java:6807)
at com ibm msg client wmq factories WMQConnectionFactory createProviderConnection(WMQConnectionFactory java:6204)
at com ibm msg client jms admin JmsConnectionFactoryImpl createConnection(JmsConnectionFactoryImpl java:278)
at com ibm mq jms MQConnectionFactory createCommonConnection(MQConnectionFactory java:6155)
at com ibm mq jms MQTopicConnectionFactory createTopicConnection(MQTopicConnectionFactory java:114)
at com ibm mq jms MQTopicConnectionFactory createConnection(MQTopicConnectionFactory java:197)
at org springframework jms support JmsAccessor createConnection(JmsAccessor java:184)
at org springframework jms listener AbstractJmsListeningContainer createSharedConnection(AbstractJmsListeningContainer java:378)
at org springframework jms listener AbstractJmsListeningContainer refreshSharedConnection(AbstractJmsListeningContainer java:363)
at org springframework jms listener DefaultMessageListenerContainer refreshConnectionUntilSuccessful(DefaultMessageListenerContainer java:785)
at org springframework jms listener DefaultMessageListenerContainer recoverAfterListenerSetupFailure(DefaultMessageListenerContainer java:767)
at org springframework jms listener DefaultMessageListenerContainer$AsyncMessageListenerInvoker run(DefaultMessageListenerContainer java:898)
at java lang Thread run(Unknown Source)
Caused by: com ibm mq MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2059' ('MQRC_Q_MGR_NOT_AVAILABLE')
at com ibm msg client wmq common internal Reason createException(Reason java:223)
14 more
Caused by: com ibm mq jmqi JmqiException: CC=2;RC=2059;AMQ9204: Connection to host 'ipaddress(1414)' rejected [1=com ibm mq jmqi JmqiException[CC=2;RC=2059;AMQ9248: The program could not bind to a 'TCP' socket [1=Socket bind,3=TCP,4=1099,5=java net BindException[Cannot assign requested address]]],3=ipaddress(1414),5=RemoteTCPConnection connnectUsingLocalAddress]
at com ibm mq jmqi remote internal RemoteFAP jmqiConnect(RemoteFAP java:1809)
at com ibm msg client wmq internal WMQConnection <init>(WMQConnection java:336)
13 more
Caused by: com ibm mq jmqi JmqiException: CC=2;RC=2059;AMQ9248: The program could not bind to a 'TCP' socket [1=Socket bind,3=TCP,4=1099,5=java net BindException[Cannot assign requested address]]
at com ibm mq jmqi remote internal RemoteTCPConnection connnectUsingLocalAddress(RemoteTCPConnection java:678)
at com ibm mq jmqi remote internal RemoteTCPConnection protocolConnect(RemoteTCPConnection java:935)
at com ibm mq jmqi remote internal system RemoteConnection connect(RemoteConnection java:1075)
at com ibm mq jmqi remote internal system RemoteConnectionPool getConnection(RemoteConnectionPool java:338)
at com ibm mq jmqi remote internal RemoteFAP jmqiConnect(RemoteFAP java:1488)
14 more
Caused by: java net BindException: Cannot assign requested address
at java net PlainSocketImpl socketBind(Native Method)
at java net PlainSocketImpl bind(Unknown Source)
at java net Socket bind(Unknown Source)
at com ibm mq jmqi remote internal RemoteTCPConnection connnectUsingLocalAddress(RemoteTCPConnection java:578) |
|
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Mar 30, 2010 6:07 am Post subject: Re: JMSWMQ0018: Failed to connect to queue manager |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mongo380 wrote: |
| HI have seen numerous posts with similar issues, but none seem to solve the problem |
But all might be the problem.
| mongo380 wrote: |
| Is there anything I need to configure on the Q manager to allow these incoming connections? Any other suggestions or things to check??? |
Define your own SVRCONN, don't use the default.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mongo380 |
| Posted: Tue Mar 30, 2010 12:41 pm Post subject: |
|
|
Newbie
Joined: 30 Mar 2010
Posts: 2
|
Thanks for your prompt reply Vitor.
Just to confirm, you suggest creating a new server-connection channel and have the client use that channel to connect to the queue manager?
Thanks again,
Mike |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 30, 2010 12:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mongo380 wrote: |
| Just to confirm, you suggest creating a new server-connection channel and have the client use that channel to connect to the queue manager? |
I am. It's unlikely (but possible) to be the cause of your problem but it's best practice to give applications their own channel. Not necessarially one per app, but at least keep them away from the SYSTEM objects.
2059 errors are probably the most common WMQ error and certainly the trickiest to track down. I can offer no better advice than to work methodically through the various causes others have reported on this forum until you find the issue.
You've already eliminated one common cause by checking it with telnet, so that's progress. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
