We are experiencing the same problem with JBoss 3.2.2 and JBoss 3.2.3. The symptom is that a MDB that has been working fine for days suddenly stops receiving messages. From the jmx-console, the queue lists 0 receivers at that time. The queue would start building up.
Based on the posts that I read, I'm going to download a new concurrent.jar that comes with 3.2.4 and see if it works. I'm also thinking about increasing the pool size of my MDB so hopefully this won't happen to all the MDB's. Is that a reasonable thing to do or am I being naive here? Thanks Adrian for your patience. Thanks for previous postings. I will post my result after I tried my solution. Did not see anybody post their results about this problem. Xibin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839366#3839366 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839366 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
