Hi Adrian, With reference to the previous posts.
We moved to JBoss3.2.3 a month back. All was going fine till today morning when we received alerts stating messages building up inspite of the MDB being active. On investigating the logs I found 2004-03-26 07:50:04,217 INFO Thread Pool Worker-496 MDB received JMS object message with JMS ID ID:31-1080287404179103 2004-03-26 07:50:04,429 INFO Thread Pool Worker-496 Processing of message [JMSMessageId=ID:31-1080287404179103] succeeded 2004-03-26 07:56:00,542 INFO Thread Pool Worker-498 MDB received JMS object message with JMS ID ID:29-1080287760462649 The single instance of MDB that we have was using different threads from Thread Pool Worker pool. Most of the time the switch was quick however in this case the MDB took 6 minutes to move to a new thread. During these 6 minutes there were around 800 messages piled up on the queue. To make things worst there were similar pauses immediately afterwards too (ranging from 40 sec to 3 mins). Is this a case of an instance of MDB being destroyed by the container to start a new instance? Or is it the server starving of execute threads? Any help would be highly appreciated. Rgds, Amresh <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827639#3827639";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827639>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
