Ignore my last post. I re-read this specific fault and noticed the first exception to start you down the path to destruction is the database commit deadlock detection.
The last post could be useful, but only if you are using persistent messages. There was a similar quirk and deadlock detection timeout that went into that rathole. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840357#3840357 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840357 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
