javax.jms.JMSException: Another thread is already in receive

[sonstone]

I have an application that has a few threads that are polling a JMS queue for work to do. When running my app, I get the following exception. I'm not really sure how to proceed with this, so any help would be greatly appreciated.


javax.jms.JMSException: Another thread is already in receive.
at org.jboss.mq.SpyMessageConsumer.receiveNoWait(SpyMessageConsumer.java
:326)
at com.netdecisions.components.decisionEngine.components.queues.JMSProce
ssQueue.getFolder(JMSProcessQueue.java:98)
at com.netdecisions.components.decisionEngine.components.queues.DefaultP
rocessRunner$ProcessRunnerLoadBalancer$ProcessRunnerThread.run(DefaultProcessRun
ner.java:220)

Thanks,

Daniel Spangler

[sonstone]

The problem with this was that I was using the same queue receiver for each thread. If you synchronize the receiveNoWait method this problem seems to go away.

[sonstone]

One last note\observation... The previous fix I mentioned solved the initial problem but it just exposed other problems. I started getting invalid transaction id exceptions. So, I would recommend not sharing a reciever among multiple threads. I don't know if this is a bug in jboss, or if it's part of the JMS spec and you just aren't supposed to do that. I'll leave that to someone else...