I am getting the same exception. We have built a large application around message queues, and send lots of messages - one to start a document to be processed and another for each stage of processing. So for each document, there are 5 or 6 messages. After a few thousand documents, we get the exception shown below.
Also because components are kept busy, they don't open and close their connection to the queues/topics for each document. Most of them are MDBs. I fail to see how this has to do with the database. Also this works just fine on Weblogic. I'm sure you aren't going to tell my your jms package is not as robust as Weblogic's, right? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834142#3834142 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834142 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
