| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2009 errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| tekgirl |
 Posted: Fri Sep 03, 2004 9:47 am Post subject: 2009 errors |
 |
|
Newbie
Joined: 02 Sep 2004
Posts: 8
Location: Madison, Wisconsin
|
When we run services for the past couple weeks, we have been getting 2009 errors in the service logs.
"RC2009 (2009)
Explanation: Connection to the queue manager has been lost. This can occur because the queue manager has ended. If the call is an MQGET call with the GMWT option, the wait has been canceled. All connection and object handles are now invalid.
For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CMPCOD of CCFAIL.
Completion Code: CCFAIL
Programmer Response: Applications can attempt to reconnect to the queue manager by issuing the MQCONN or MQCONNX call. It may be necessary to poll until a successful response is received.
Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically."
We are getting this after many of the messages have been successfully sent....i.e. it will send 10 successfully maybe and error out on the rest. The qmgr is NOT down, the server does not appear to have any connectivity issues (in fact, the services are running directly on the same server as the qmgr).
Here's the log from one of the services:
MQJE001: An MQException occurred: Completion Code 2, Reason 2009
INFO | jvm 1 | 2004/09/03 12:11:53 | MQJE016: MQ queue manager closed channel immediately during connect
INFO | jvm 1 | 2004/09/03 12:11:53 | Closure reason = 2009
INFO | jvm 1 | 2004/09/03 12:11:53 | MQJE001: Completion Code 2, Reason 2009
INFO | jvm 1 | 2004/09/03 12:11:53 | com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
INFO | jvm 1 | 2004/09/03 12:11:53 | at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:172)
INFO | jvm 1 | 2004/09/03 12:11:53 | at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:270)
INFO | jvm 1 | 2004/09/03 12:11:53 | at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:290)
INFO | jvm 1 | 2004/09/03 12:11:53 | at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
INFO | jvm 1 | 2004/09/03 12:11:53 | at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:150)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:682)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:393)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.wea.logging.edi.MQAppender.append(MQAppender.java:64)
INFO | jvm 1 | 2004/09/03 12:11:59 | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
INFO | jvm 1 | 2004/09/03 12:11:59 | at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
INFO | jvm 1 | 2004/09/03 12:11:59 | at org.apache.log4j.Category.callAppenders(Category.java:187)
INFO | jvm 1 | 2004/09/03 12:11:59 | at org.apache.log4j.Category.forcedLog(Category.java:372)
INFO | jvm 1 | 2004/09/03 12:11:59 | at org.apache.log4j.Category.info(Category.java:674)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.wea.logging.edi.client.EdiEventHandler.info(EdiEventHandler.java:61)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.wea.edi.controller.BatchIdServiceController.onMessage(BatchIdServiceController.java:55)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.wea.mq.controller.CommonMQController.process(CommonMQController.java:129)
INFO | jvm 1 | 2004/09/03 12:11:59 | at com.wea.mq.controller.CommonMQController.run(CommonMQController.java:252)
INFO | jvm 1 | 2004/09/03 12:11:59 | Returned from Service Controllerclass com.wea.edi.controller.BatchIdServiceController
STATUS | wrapper | 2004/09/03 12:13:23 | <-- Wrapper Stopped.
We have been troubleshooting this & I am at a loss as to what is causing this.....is it java, api, mq, etc, etc...
Any suggestions would be great! |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Sep 03, 2004 10:30 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| A 2009 is a connection broken and it can happen for various reasons. If you are only seeing it every now and then over the last few weeks, I'd suspect some kind of glitch in the network. |
|
| Back to top |
|
|
| tekgirl |
| Posted: Tue Sep 07, 2004 10:20 am Post subject: ya but |
|
|
Newbie
Joined: 02 Sep 2004
Posts: 8
Location: Madison, Wisconsin
|
"(in fact, the services are running directly on the same server as the qmgr). "
and there is nothing indicative of connectivity issues in any logs (on the switch, network monitoring, the server itself, etc.).
I guess I am wondering if it could be something wrong with the service itself or something.
Thanks for the reply! |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Sep 07, 2004 10:41 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Are you using client or bindings mode? |
|
| 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
|
|
|
|
