I experienced this problem in 1.4.0.GA due to JBMESSAGING-1159, but it went away after I hot-patched just that fix into the 1.4.0.GA jar.
Maybe your maxSession is too high? Try sticking a "@PoolClass(value=StrictMaxPool.class, maxSize=1024, timeout=1000)" on your MDB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120050#4120050 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120050 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
