MQSeries.net :: View topic - Unique problem..MDB just stops processing

tarunmq1 · Posted: Tue Oct 07, 2008 2:37 am Post subject:

Hi All,

My situation

I have two MDBs running pointing to two different Q Managers.
Due to message affinity, I can only run one instance at a time.
Every now and then, one MDB just stops processing the messages (and its the same MDB every time) The other MDB keeps running fine. The messages start to pile up in this one queue and then when we bounce it, it works fine. The listener ports never get stopped.

I don't see any exceptions in the logs so can't really put a handle on what's going wrong where.

We thought may be the connections weren't enough so we increased the connection pool from 10 to 20 but that didn't help.

Is it because its only one session and it gets destroyed or something?

Is there a way I can enable tracing on the MDB level?
I am using MQ5.3 w/ WAS5.1.

In case of JMS exception, i am rolling back the transaction. Does that mean the message is put back on the Q?

I have a backout threshold property set to 2 and a backout Q defined. and the listener port retries property is to the max # so my understanding is that after 2 retries it should send the message to the backout Q.

It happens only on production. Never experienced it on QA or any other environment.

I am attaching the code of my MDB
===========================

public void onMessage(javax.jms.Message msg) {

String xmlMsg = null;

if(msg instanceof TextMessage) {

try {

xmlMsg = ((TextMessage) msg).getText();
MsgLogger.logSPSRecvMsg(xmlMsg);
XXXFactory.processMessage(xmlMsg);

} catch (XmlException e) {
MsgLogger.logRejectedMsg(xmlMsg);
XXXLogger.MQ.fatal("XmlException caught " + e);
e.printStackTrace();

} catch (JMSException e) {
XXXLogger.MQ.fatal("JMSException caught " + e);
fMessageDrivenCtx.setRollbackOnly();
e.printStackTrace();
}
catch (Throwable e) {
XXXLogger.MQ.fatal("Throwable caught " + e);
XXXLogger.MQ.fatal("FAILED TO PROCESS THIS MESSAGE " + xmlMsg);
e.printStackTrace();
}

}
else {

XXXLogger.MQ.fatal("FAILED TO PROCESS THIS MESSAGE -- WAS NOT OF TYPE TEXT MESSAGE " + xmlMsg);
}
}
========================================

The other MDB (which works fine) has pretty much the same code.

Please let me know if you need me to provide more info..

Please help!!!!!!!

Thanks in advance,