Author:
MANT
Message:
Matt,
Do you think the issue could be with the Thread pool? The stacktrace is
pointing to the below log that starts with a Thread pool class
..WMQCommonservices and WebContainer threadpool size for our app is at default
currrently....???
.
.
.
.
at
com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1093)
at
com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:778)
at $Proxy48.onMessage(Unknown Source)
at
com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)
at
com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:147)
at
com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2639)
at com.ibm.mq.jms.MQSession.run(MQSession.java:862)
at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:229)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
the
To respond to this post, please click the following link:
<http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14674245>
____________________________________
Unsubscribe via the "binocular" icon on the web
