|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Getting MQJE001: Completion Code 2, Reason 2009 |
« View previous topic :: View next topic » |
Author |
Message
|
gnanasekaran.g |
Posted: Wed Feb 28, 2007 2:33 am Post subject: Getting MQJE001: Completion Code 2, Reason 2009 |
|
|
Newbie
Joined: 27 Feb 2007 Posts: 1
|
Hi,
I am having JBoss server 3.2.8.SP1, which is communication with IBM Websphere MQ Series verson 5.3.
I cant able to receive message from Queue and getting the Error as "MQJE001: Completion Code 2, Reason 2009".
Why this error is coming?I am not getting this error oftenly but daily two times or three times.I was forced to shoutdown the JBoss server and receiving properly , when JBoss is shoutdown and restarts.
My J2EE Application runs in my local machine(i.e.JBoss running in my machine) and IBM Websphere is running in another machine.
Through many forums i searched qm.ini and couldnt find this one.But some ini files in websphere are as follows :
[img]C:\Documents and Settings\contact admin\Desktop\mqparams.ini files.bmp
to configure some stanza.
Please any one let me know how to overcome this problem.
How the server is receiving the messages when restarting and why it is not happening at normal.why it is forcing me to do shutdown and restart the server.really headache to me.This application is a multithreading operation and i am storing these messages in database after taken from queue.
Here is the Complete list of Exception :
1.
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage:com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:172)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:270)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:290)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:150)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:682)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:393)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.objectfrontier.rtgs.server.piclient.bo.DefaultJMSConsumer.selectQMgr(DefaultJMSConsumer.java:392)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.objectfrontier.rtgs.server.piclient.bo.DefaultJMSConsumer.receiveMessage(DefaultJMSConsumer.java:140)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.objectfrontier.rtgs.server.piclient.bo.ListenerHandleTask.startListenerTask(ListenerHandleTask.java:180)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.objectfrontier.rtgs.server.piclient.bo.ListenerHandleTask.startListener(ListenerHandleTask.java:150)
02/21/07 02-45:Thread-31:DefaultJMSConsumer:receiveMessage: at com.objectfrontier.rtgs.server.piclient.bo.ListenerHandleTask.run(ListenerHandleTask.java:76)
2.
02/21/07 02-46:Thread-17:DefaultJMSMessageProducer:queueSendMessage:Error occurs while putting the message in MQcom.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
3.
02/21/07 03-04:Thread-122:DefaultJMSMessageProducer:queueSendMessage:Error occurs while putting the message in MQcom.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process:Unexpected interrupt of sleep occured
02/21/07 03-04:Thread-121:DefaultJMSMessageProducer:queueSendMessage:Error occurs while putting the message in MQcom.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process:Unexpected interrupt of sleep occured
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process:java.lang.RuntimeException: Unable to send Message
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.notification.jms.DefaultJMSMessageProducer.queueSendMessage(DefaultJMSMessageProducer.java:410)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.notification.jms.DefaultJMSMessageProducer.notify(DefaultJMSMessageProducer.java:269)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.piclient.bo.MessageRedirect.redirectToTrashQueue(MessageRedirect.java:131)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.bo.InwardMsgHandlerBOImpl.handleMessage(InwardMsgHandlerBOImpl.java:227)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.bo.InwardMsgHandlerBOImpl.handleMessage(InwardMsgHandlerBOImpl.java:173)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.workflow.bo.InwardWorkflowHandleTask.process(InwardWorkflowHandleTask.java:108)
02/21/07 03-04:Thread-122:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.service.resourcepool.AbstractThreadResource.run(AbstractThreadResource.java:67)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process:java.lang.RuntimeException: Unable to send Message
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.notification.jms.DefaultJMSMessageProducer.queueSendMessage(DefaultJMSMessageProducer.java:410)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.notification.jms.DefaultJMSMessageProducer.notify(DefaultJMSMessageProducer.java:269)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.piclient.bo.MessageRedirect.redirectToTrashQueue(MessageRedirect.java:131)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.bo.InwardMsgHandlerBOImpl.handleMessage(InwardMsgHandlerBOImpl.java:227)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.bo.InwardMsgHandlerBOImpl.handleMessage(InwardMsgHandlerBOImpl.java:173)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.rtgs.server.workflow.bo.InwardWorkflowHandleTask.process(InwardWorkflowHandleTask.java:108)
02/21/07 03-04:Thread-121:InwardWorkflowHandleTask:process: at com.objectfrontier.arch.service.resourcepool.AbstractThreadResource.run(AbstractThreadResource.java:67) |
|
Back to top |
|
 |
RogerLacroix |
Posted: Wed Feb 28, 2007 9:18 am Post subject: Re: Getting MQJE001: Completion Code 2, Reason 2009 |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
contact admin.g wrote: |
I am having JBoss server 3.2.8.SP1, which is communication with IBM Websphere MQ Series verson 5.3.
I cant able to receive message from Queue and getting the Error as "MQJE001: Completion Code 2, Reason 2009".
Why this error is coming?I am not getting this error oftenly but daily two times or three times.I was forced to shoutdown the JBoss server and receiving properly , when JBoss is shoutdown and restarts.
My J2EE Application runs in my local machine(i.e.JBoss running in my machine) and IBM Websphere is running in another machine.
Through many forums i searched qm.ini and couldnt find this one.But some ini files in websphere are as follows :
[img]C:\Documents and Settings\contact admin\Desktop\mqparams.ini files.bmp
to configure some stanza.
Please any one let me know how to overcome this problem.
How the server is receiving the messages when restarting and why it is not happening at normal.why it is forcing me to do shutdown and restart the server.really headache to me.This application is a multithreading operation and i am storing these messages in database after taken from queue. |
The #1 cause for reason code of 2009 for a Web application is that it is leaking connections or the max connection pool value is set way too high or there is no max connection pool value, hence it is unlimited.
This problem has been discussed here many, many times before. (try the search button)
The default max number of channels for a queue manager is 100. Try changing it to 200. If the Web app again gets rc=2009 then you know there is connection pool problem.
On the server where the queue manager is running, do the following to count the number of connections:
Code: |
netstat -an | grep 1414 |wc -l |
Regards,
Roger Lacroix
Capitalware Inc. _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
 |
ganeshr2 |
Posted: Tue Mar 20, 2007 10:47 am Post subject: |
|
|
Newbie
Joined: 20 Mar 2007 Posts: 1
|
RogerLacroix
[quote]
The default max number of channels for a queue manager is 100. Try changing it to 200. If the Web app again gets rc=2009 then you know there is connection pool problem.
[/quote]
If we change the max number of channel will there be any performance hit to the application.
we are seeing max number of channel error in our application occationally.
Thanks.... |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 20, 2007 12:34 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
#3
Quote: |
MQJE001: Completion Code 2, Reason 2085 |
see 2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME
Enjoy  _________________ MQ & Broker admin |
|
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
|
|
|
|