Did you mean to post this on user list rather than the dev list? This looks like some other error occurred and the test is not handling shutdown correctly.
I keep meaning to tidyup the JBossMQ base tests they don't even close the connections properly in the event of failure (no finally block) ;-( It doesn't matter for JUnit because it forks a process and the OS closes the socket at process end, but it makes getting the real hard. Can you add TRACE logging for org.jboss.mq to testsuite/output/test.log and post the result for running the "one-test" as a bug report. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921651#3921651 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921651 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
