| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ error WebSphere MQ call failed with compcode '2' - 2009 |
« View previous topic :: View next topic » |
| Author |
Message
|
| steiner |
 Posted: Wed Mar 06, 2013 2:10 am Post subject: MQ error WebSphere MQ call failed with compcode '2' - 2009 |
 |
|
Voyager
Joined: 07 Mar 2003
Posts: 89
|
Hello,
we have received that Error between Was and MQSeries in the WAS SystemOut.log.
I check and qmgr and queues are Ok - Right Configuration
In the IBM knowledge base i didn't found any acceptable information about the error :
com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
I suppose it's a Problem with our listener but i'm not sure because we are in MQSeries Version Version: 7.0.1.3 CMVC level: p701-103-100813
Could you explain me where is the Problem
Thanks a lot...
| Code: |
===============================================
2013-02-21 06:02:37,859 [COREBUSLUX - GETTABLEDATA - COREBUSLUX13614229575760] [ERROR] com.dexiabil.ginko.senseo.transformer.schema.SchemaDispatcherImpl.getVerifier(106) | Cannot find verifier for 'com/dexiabil/corebusiness/table/xsd/GetTableResponse.xsd'com.dexiabil.ginko.senseo.transformer.schema.SchemaException: Cannot find xsd at path 'com/dexiabil/corebusiness/table/xsd/GetTableResponse.xsd'
[2/21/13 6:02:48:239 CET] 00000021 SibMessage W [:] CWSJY0003W: JMSCC3036: An exception has been delivered to the connections exception listener: '
Message : com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A problem with this connection has occurred. An error has occurred with the WebSphere MQ JMS connection. Use the linked exception to determine the cause of this error.
Class : class com.ibm.msg.client.jms.DetailedJMSException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:608)
: com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:236)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1100)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1063)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.access$800(WMQMessageProducer.java:71)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer$SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:824)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.<init>(WMQMessageProducer.java:1038)
: com.ibm.msg.client.wmq.internal.WMQSession.createProducer(WMQSession.java:980)
: com.ibm.msg.client.jms.internal.JmsSessionImpl.createProducer(JmsSessionImpl.java:1191)
: com.ibm.msg.client.jms.internal.JmsXAQueueSessionImpl$1.createSender(JmsXAQueueSessionImpl.java:415)
: com.ibm.mq.jms.MQQueueSession.createSender(MQQueueSession.java:148)
: com.ibm.ejs.jms.JMSQueueSenderHandle.<init>(JMSQueueSenderHandle.java:101)
: com.ibm.ejs.jms.JMSQueueSessionHandle.createSender(JMSQueueSessionHandle.java:234)
: org.springframework.jms.core.JmsTemplate102.doCreateProducer(JmsTemplate102.java:196)
: org.springframework.jms.core.JmsTemplate.createProducer(JmsTemplate.java:952)
: org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:563)
: org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:536)
: org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
: org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:534)
: org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:641)
: com.dexiabil.ginko.connector.JmsConnector.put(JmsConnector.java:204)
: com.dexiabil.ginko.connector.JmsConnector.sendMessage(JmsConnector.java:241)
: com.dexiabil.ginko.connector.JmsConnector.sendNonSyncMessage(JmsConnector.java:91)
: com.dexiabil.ginko.connector.service.ESBConnector.sendMessage(ESBConnector.java:380)
: com.dexiabil.ginko.connector.service.ESBConnector.sendResponse(ESBConnector.java:321)
: sun.reflect.GeneratedMethodAccessor34.invoke(null:-1)
: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
: java.lang.reflect.Method.invoke(Method.java:600)
: com.dexiabil.ginko.scenario.StepImpl.execute(StepImpl.java:79)
: com.dexiabil.ginko.processflowmanager.ProcessFlowExecuterImpl.executeStep(ProcessFlowExecuterImpl.java:82)
: com.dexiabil.ginko.processflowmanager.ProcessFlowExecuterImpl.executeScenario(ProcessFlowExecuterImpl.java:131)
: com.dexiabil.ginko.processflowmanager.ProcessFlowManagerImpl.execute(ProcessFlowManagerImpl.java:196)
: com.dexiabil.ginko.requestbroker.implementation.RequestBrokerImpl.execute(RequestBrokerImpl.java:210)
: com.dexiabil.ginko.Ginko.execute(Ginko.java:348)
: com.dexiabil.ginko.Ginko.execute(Ginko.java:378)
: com.dexiabil.ginko.senseo.SenseoAgent.onMessage(SenseoAgent.java:235)
: com.dexiabil.senseo.mdb.AbstractSenseoMDB.onTextMessage(AbstractSenseoMDB.java:53)
: com.dexiabil.senseo.mdb.AbstractSenseoMDB.handleMessage(AbstractSenseoMDB.java:44)
: com.dexiabil.eer.senseo.mdbs.MDBCOREBUS.onMessage(MDBCOREBUS.java:34)
: com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:302)
: com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
: com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:268)
: com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:240)
: com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:147)
: com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2639)
: com.ibm.msg.client.jms.internal.JmsXAQueueSessionImpl$1.run(JmsXAQueueSessionImpl.java:395)
: com.ibm.mq.jms.MQSession.run(MQSession.java:862)
: com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:1045)
: com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:1076)
: com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:746)
: com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:712)
: sun.reflect.GeneratedMethodAccessor31.invoke(null:-1)
: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
: java.lang.reflect.Method.invoke(Method.java:600)
: com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:44)
: com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:100)
: com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:136)
: com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:567)
: com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
Class : class com.ibm.mq.MQException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1100)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1063)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.access$800(WMQMessageProducer.java:71)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer$SpiIdentifiedProducerShadow.initialise(WMQMessageProducer.java:824)
: com.ibm.msg.client.wmq.internal.WMQMessageProducer.<init>(WMQMessageProducer.java:1038)
: com.ibm.msg.client.wmq.internal.WMQSession.createProducer(WMQSession.java:980)
: com.ibm.msg.client.jms.internal.JmsSessionImpl.createProducer(JmsSessionImpl.java:1191)
: com.ibm.msg.client.jms.internal.JmsXAQueueSessionImpl$1.createSender(JmsXAQueueSessionImpl.java:415)
: com.ibm.mq.jms.MQQueueSession.createSender(MQQueueSession.java:148)
: com.ibm.ejs.jms.JMSQueueSenderHandle.<init>(JMSQueueSenderHandle.java:101)
: com.ibm.ejs.jms.JMSQueueSessionHandle.createSender(JMSQueueSessionHandle.java:234)
: org.springframework.jms.core.JmsTemplate102.doCreateProducer(JmsTemplate102.java:196)
: org.springframework.jms.core.JmsTemplate.createProducer(JmsTemplate.java:952)
: org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:563)
: org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:536)
: org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
: org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:534)
: org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:641)
: com.dexiabil.ginko.connector.JmsConnector.put(JmsConnector.java:204)
: com.dexiabil.ginko.connector.JmsConnector.sendMessage(JmsConnector.java:241)
: com.dexiabil.ginko.connector.JmsConnector.sendNonSyncMessage(JmsConnector.java:91)
: com.dexiabil.ginko.connector.service.ESBConnector.sendMessage(ESBConnector.java:380)
: com.dexiabil.ginko.connector.service.ESBConnector.sendResponse(ESBConnector.java:321)
: sun.reflect.GeneratedMethodAccessor34.invoke(null:-1)
: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
: java.lang.reflect.Method.invoke(Method.java:600)
: com.dexiabil.ginko.scenario.StepImpl.execute(StepImpl.java:79)
: com.dexiabil.ginko.processflowmanager.ProcessFlowExecuterImpl.executeStep(ProcessFlowExecuterImpl.java:82)
: com.dexiabil.ginko.processflowmanager.ProcessFlowExecuterImpl.executeScenario(ProcessFlowExecuterImpl.java:131)
: com.dexiabil.ginko.processflowmanager.ProcessFlowManagerImpl.execute(ProcessFlowManagerImpl.java:196)
: com.dexiabil.ginko.requestbroker.implementation.RequestBrokerImpl.execute(RequestBrokerImpl.java:210)
: com.dexiabil.ginko.Ginko.execute(Ginko.java:348)
: com.dexiabil.ginko.Ginko.execute(Ginko.java:378)
: com.dexiabil.ginko.senseo.SenseoAgent.onMessage(SenseoAgent.java:235)
: com.dexiabil.senseo.mdb.AbstractSenseoMDB.onTextMessage(AbstractSenseoMDB.java:53)
: com.dexiabil.senseo.mdb.AbstractSenseoMDB.handleMessage(AbstractSenseoMDB.java:44)
: com.dexiabil.eer.senseo.mdbs.MDBCOREBUS.onMessage(MDBCOREBUS.java:34)
: com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:302)
: com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
: com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:268)
: com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:240)
: com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:147)
: com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2639)
: com.ibm.msg.client.jms.internal.JmsXAQueueSessionImpl$1.run(JmsXAQueueSessionImpl.java:395)
: com.ibm.mq.jms.MQSession.run(MQSession.java:862)
: com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:1045)
: com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:1076)
: com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:746)
: com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:712)
: sun.reflect.GeneratedMethodAccessor31.invoke(null:-1)
: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
: java.lang.reflect.Method.invoke(Method.java:600)
: com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:44)
: com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:100)
: com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:136)
: com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:567)
: com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
'.
[2/21/13 6:02:48:248 CET] 00000021 ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
[2/21/13 6:02:48:257 CET] 00000021 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource JMS$COREBUSLUX$JMSManagedConnection@90. The exception is: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2008: Failed to open MQ queue 'COREBUSLUX.TO.ESB'. JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
[2/21/13 6:02:48:262 CET] 00000021 ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
[2/21/13 6:02:48:266 CET] 00000021 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jms/connfactory/COREBUSLUX. The exception is: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2008: Failed to open MQ queue 'COREBUSLUX.TO.ESB'. JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
[2/21/13 6:02:48:439 CET] 00000021 DMAdapter I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /APPLICATIONS/WebSphere/Profiles/bilws10p/properties/logbr/ffdc/adv/ffdcdb.xml
[2/21/13 6:02:48:446 CET] 00000021 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /APPLICATIONS/WebSphere/Profiles/bilws10p/logs/ffdc/CoreBusinessServicesJVM_3cf03cf_13.02.21_06.02.48.4234303400061090208440.txt com.ibm.ejs.jms.JMSQueueSenderHandle.JMSQueueSenderHandle 83
[2/21/13 6:02:48:469 CET] 00000021 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /APPLICATIONS/WebSphere/Profiles/bilws10p/logs/ffdc/CoreBusinessServicesJVM_3cf03cf_13.02.21_06.02.48.4666489108925189185830.txt com.ibm.ejs.jms.JMSQueueSessionHandle.createSender 223
[2/21/13 6:02:48:476 CET] 00000021 SystemOut O
2013-02-21 06:02:48,476 [COREBUSLUX - GETTABLEDATA - COREBUSLUX13614229575760] [ERROR] com.dexiabil.ginko.connector.JmsConnector.put(212) | Error sending message on queue : queue:///COREBUSLUX.TO.ESB?putAsyncAllowed=1&readAheadAllowed=1
[2/21/13 6:02:48:477 CET] 00000021 SystemOut O
2013-02-21 06:02:48,477 [COREBUSLUX - GETTABLEDATA - COREBUSLUX13614229575760] [ERROR] com.dexiabil.ginko.connector.JmsConnector.sendMessage(220) | Error sending message on queue queue:///COREBUSLUX.TO.ESB?putAsyncAllowed=1&readAheadAllowed=1
org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2008: Failed to open MQ queue 'COREBUSLUX.TO.ESB'. JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
=============================================== |
|
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Mar 06, 2013 2:58 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
steiner, I've code-enclosed your dump output as it makes it easier to read. Basically, the network connection between your WAS instance and the queue manager has dropped and your WAS instance has not automatically disconnected/reconnected, and you have not stated which version of WAS you are using.
I'm not familiar with WAS but I would expect the later versions to have the WMQ client automatic-reconnect feature that was introduced with WMQ V7.0. I'm sure someone more WAS-aware will be along to put us both straight 
_________________
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 |
|
|
| steiner |
| Posted: Wed Mar 06, 2013 5:11 am Post subject: MQ error WebSphere MQ call failed with compcode '2' - 2009 |
|
|
Voyager
Joined: 07 Mar 2003
Posts: 89
|
Hello,
Thanks for your answer.
yes we are in WAS 7.00.13.
My question is : do you think we could apply a patch on MQ to solve that problem
Thanks, bye |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 06, 2013 5:37 am Post subject: Re: MQ error WebSphere MQ call failed with compcode '2' - 20 |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| steiner wrote: |
| My question is : do you think we could apply a patch on MQ to solve that problem |
The issue is not with WMQ it's with WAS not automatically reconnecting, so applying maintenance to WMQ is not going to solve the WAS instance not recovering from a broken connection. That said, it does no harm to be at the latest (or at least n-1) level of WMQ.
Edit: Also moved this to a more appropriate forum.
_________________
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 |
|
|
| brianb |
| Posted: Tue Mar 19, 2013 7:03 pm Post subject: |
|
|
Voyager
Joined: 12 May 2010
Posts: 85
|
Hi
2009 will usually generate an FDC
Look in the MQ error directory and see if there is an FDC
Then google the Probe ID |
|
| 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
|
|
|
|
