Posted: Fri Feb 09, 2007 9:51 am Post subject: ME71
Newbie
Joined: 17 Jul 2006 Posts: 4
hi all,
we are seeing a issue where the listener ports for the applicatiin on WAS are shutting down after they see the following exception
[1/30/07 10:31:35:410 EST] 0000004f FreePool E J2CA0046E: Method createManagedConnectionWithMCWrapper caught an exception during creation of the ManagedConnection for resource JMS$mq_ocs_exs_qcf$JMSManagedConnection@1118844344, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: Failed to create session
at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException(JMSCMUtils.java:127)
at com.ibm.ejs.jms.JMSManagedSession.<init>(JMSManagedSession.java:247)
at com.ibm.ejs.jms.JMSManagedQueueSession.<init>(JMSManagedQueueSession.java:56)
at com.ibm.ejs.jms.JMSManagedQueueSessionFactory.createManagedSession(JMSManagedQueueSessionFactory.java:45)
at com.ibm.ejs.jms.JMSManagedSessionFactory.createManagedConnection(JMSManagedSessionFactory.java:424)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1294)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:2000)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:769)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:569)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createListenerQueueSession(JMSQueueConnectionHandle.java:251)
at com.ibm.ejs.jms.listener.ServerSession.<init>(ServerSession.java:246)
at com.ibm.ejs.jms.listener.ServerSessionPool.getServerSession(ServerSessionPool.java:239)
at com.ibm.mq.jms.MQConnectionConsumer$MQConnectionConsumerMRH.deliverNow(MQConnectionConsumer.java:213)
at com.ibm.mq.jms.MQConnectionConsumer$MQConnectionConsumerMRH.endDeliver(MQConnectionConsumer.java:121)
at com.ibm.mq.jms.MQConnectionBrowser.endDeliver(MQConnectionBrowser.java:810)
at com.ibm.mq.jms.MQQueueAgent.startBrowsers(MQQueueAgent.java:1334)
at com.ibm.mq.jms.MQQueueAgentThread.deliverNow(MQQueueAgentThread.java:1661)
at com.ibm.mq.jms.MQQueueAgentThread1Impl.browse(MQQueueAgentThread1Impl.java:268)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1553)
at java.lang.Thread.run(Thread.java:568)
Caused by: javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1685)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1129)
at com.ibm.mq.jms.MQQueueConnection.createQueueSession(MQQueueConnection.java:490)
at com.ibm.mq.jms.MQQueueConnection.createQueueSession(MQQueueConnection.java:234)
at com.ibm.ejs.jms.JMSManagedQueueSession.createSession(JMSManagedQueueSession.java:110)
at com.ibm.ejs.jms.JMSManagedSession.<init>(JMSManagedSession.java:214)
... 19 more
we have
MQ version: 5.3.1
WAS version: 6
WAS listener port retry count :0
Queue back out count:4
we use ME71 security exit .
I believe the exception is from security exit and increasing the retry count on listenerport would let the WAS listener port retry for couple of times. Is there a way we can make the listener port handle this scenario instead of stopping after couple of retries.
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