We solved this problem. Turns out it has nothing to do with JBoss Messaging and
everything to do with our code. I'm relating our experiences here in case
anyone else encounters a similar problem.
Queue clients are not only a JBoss server hosting MDB's listening to those
queues, but also
Good analysis.
How did you resolve?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033217#4033217
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033217
___
jboss-user mailing
Well the solution was breaking the deadlock, which is application specific. As
long as the QueueConnection could be reestablished, the deadlock would be
broken.
We stopped implementing message receive as a MessageListener and did it
ourselves. This had the effect that we could control when
Thread A was the onMessage() thread.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033227#4033227
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033227
___
jboss-user mailing
