I have seen similar issues before when a jms session is being used by 2 or more threads
concurrently.
E.g. two threads doing consumer.receive() concurrently/
JMS sessions are only meant to be used by one thread at a time.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000100#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...