out of 8 queues in production one queue suddenly stopped consuming

[santhoshreddy747]

Hi we have a 8 queues in my production invironment on jboss 3.2.7 server.All the queues are consumed by the MDB suddenly one queue is

suddenly stopped consuming.I dont have idea why it was stopped suddenly. Thanks for any help.Im also attaching my MDB code.

please see the below log file:

INFO: Send the message successfully to GTX </ns1:ApplicationMessage>
2010-07-16 09:21:21,300 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GTXSOAPCalling callingGtxSoapProcess
INFO: Send the message successfully to GTX </xmlString></m:ReceiveApplicationFeedBackMessageProcessResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
2010-07-16 09:21:21,454 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GtxEskomFourthInstanceMDB onMessage
INFO: Received JMS message (ID:121876-12792641684771) from Queue (ApplicationMessageInBoundQueue).
2010-07-16 09:21:21,454 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GtxEskomFourthInstanceMDB onMessage
INFO: MESSAGE BEAN: Got the message Type :  ApplicationFeedBackMessage and SoapTargetValue :  http://localhost:11280/GTConnect/StatelessSoapAcceptor/?gtxInitialProcess=EskomObjectLayer.IntegrationObjects.Processes.SOAPReceivers.ReceiveApplicationFeedBackMessage
2010-07-16 09:21:21,455 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GetSoapXmlByMsgType getMessageType
INFO: MESSAGE BEAN: inside getMessageType :ApplicationFeedBackMessage
2010-07-16 09:21:21,455 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GetSoapXmlByMsgType getMessageType
INFO: MESSAGE BEAN: inside ApplicationFeedBackMessage :
2010-07-16 09:21:21,456 INFO  [STDOUT] Jul 16, 2010 9:21:21 AM za.eskom.jms.ejb.GtxEskomFourthInstanceMDB onMessage
INFO: MESSAGE BEAN: Calling Gtx Soap process :
2010-07-16 09:21:21,682 WARN  [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=mp2hs104.eskom.co.za//201247, BranchQual=] timed out. status=STATUS_ACTIVE
2010-07-16 09:21:21,693 WARN  [org.jboss.mq.SpyConnectionConsumer] Connection consumer closing due to error in listening thread SpyConnectionConsumer[sub=Subscription[subId=-2147483648connection=ConnectionToken:ID:123967/c38ccd7bb57f0c3aa211115d49666df1 destination=QUEUE.ApplicationMessageInBoundQueue messageSelector=null Local Create] messages=0 waitingForMessage=false internalThread=Thread[Connection Consumer for dest Subscription[subId=-2147483648connection=ConnectionToken:ID:123967/c38ccd7bb57f0c3aa211115d49666df1 destination=QUEUE.ApplicationMessageInBoundQueue messageSelector=null Local Create] id=36,5,jboss] sessionPool=org.jboss.jms.asf.StdServerSessionPool@12d479f connection=Connection@20308548[token=ConnectionToken:ID:123967/c38ccd7bb57f0c3aa211115d49666df1 rcvstate=STARTED]]
javax.jms.JMSException: Failed to get a server session: javax.jms.JMSException: Cannot get session after pool has been closed down.
        at org.jboss.jms.asf.StdServerSessionPool.getServerSession(StdServerSessionPool.java:206)
        at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:294)
        at java.lang.Thread.run(Thread.java:534)
2010-07-16 09:21:24,938 INFO  [STDOUT] Jul 16, 2010 9:21:24 AM za.eskom.jms.ejb.GtxEskomSecondInstanceMDB onMessage
SEVERE: Failed to submit JMS message  with an exception - Connection timed out (errno:238)
2010-07-16 09:21:24,948 INFO  [STDOUT] Jul 16, 2010 9:21:24 AM za.eskom.jms.ejb.GtxEskomSecondInstanceMDB onMessage
INFO: Received JMS message (ID:121048-12792639121082) from Queue (WorkRequestInBoundQueue).
2010-07-16 09:21:24,949 INFO  [STDOUT] Jul 16, 2010 9:21:24 AM za.eskom.jms.ejb.GtxEskomSecondInstanceMDB onMessage
INFO: MESSAGE BEAN: Got the message Type :  WorkRequestMessage and SoapTargetValue :  http://localhost:9280/GTConnect/StatelessSoapAcceptor/?gtxInitialProcess=EskomObjectLayer.IntegrationObjects.Processes.SOAPReceivers.ReceiveWorkRequestFeedbackMessage
2010-07-16 09:21:24,949 INFO  [STDOUT] Jul 16, 2010 9:21:24 AM za.eskom.jms.ejb.GetSoapXmlByMsgType

[santhoshreddy747]

Hi,

We solved this probelm actualy nothing to do with MDB or nothing to do with jboss.It is the code going to infinite loop.It is no more taking the messages from MDB.

Thanks

santhosh