Bugs item #491613, was opened at 2001-12-11 08:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=491613&group_id=22866
Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Christian Riege (lqd) Assigned to: Hiram Chirino (chirino) Summary: Server stops delivering messages to MDBs Initial Comment: hi, we found a very hard to reproduce bug in JBossMQ; it *might* be a race condition. We tracked the problem down to the interaction between org.jboss.mq.server.BasicQueue and org.jboss.mq.SpyConnectionConsumer. Here's what happens: SpyConnectionConsumer.java reaches line 105 (commented "unwanted msg") and delivers a NACK. BasicQueue.java receives the NACK and tries to restore the message using the restoreMessage() method. However, from that point of time *NO* receiver is being added to the receivers list in BasicQueue.java, resulting in the internal message queue growing without EVER delivering any messages anymore. This *only* happens when Line 105 in SpyConnectionConsumer.java is invoked -- if my MDB calls setRollbackOnly(), everything continues working. As I said, this is *very* hard to reproduce and my guess is on a race condition. We tried to fix this on our own but got lost in the MQ magic. P.S.: Running JBoss 2.4.4 CVS as of today but this bug has been in before as it seems, we're getting the same behaviour on a vanilla 2.4.3 configuration. I'll try to come up with a testcase if you need it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=491613&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
