As much logging as possible would help.
IIRC some of those app server tests are very bad at clearing up their state. Perhaps a
previous test has left behind a consumer after not closing its connection properly, and
that consumer has nabbed the message instead of the one you expect. (I've seen this
kind of thing before)
The server will eventually time out and close unclosed sessions, but if the next test
kicks in before this occurs you might end up with these kind of issues.
Just a thought.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176199#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...