Thank you, nice hint :) The business method on the bean that sends the message had TransactionAttributeType.SUPPORTED, I just set it to TransactionAttributeType.REQUIRED and it works now.
James.Strachan wrote: > > On 23/01/2008, Demian Mrakovich <[EMAIL PROTECTED]> wrote: >> >> This is driving me crazy... >> >> I am running ActiveMQ under JBoss, and I have one dispatcher EJB3 bean >> which >> sends to a queue and one message-driven bean connecting to the same >> queue. I >> call a method on my dispatcher bean which posts a message to the queue >> and >> it gets picked up by the MD bean just fine. Then I call the same method >> on >> the same dispatcher bean from somewhere else, now onMessage is never >> invoked >> on the MD bean. Note that both calls go through the exact same piece of >> code >> for sending the message. Yet the message never arrives on the latter >> call. >> >> Any hints for me? > > Does your transaction ever commit in the 2nd case? > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/onMessage-does-not-get-called-tp15048483s2354p15063645.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
