Originally posted by Mikalai Zaikin:
My understanding is, that EJB container delay JMS transmitting until transaction will be commited, so specification says that developer should not rely on request-response techique of JMS inside one transaction, because request JMS will not be delivered until transaction commited.
Originally posted by Brian Nice:
Are you talking about the so called "Poison" messages, where the MDB gets the message and calls an entity bean which is in a transaction, and a rollback occurs so the MDB tries to resend the message generating an infinite loop? What is the best way to handle something like that?