I have a application with 1 EJB and 2 spring Bean Services.
We use Container Managed Transactions.
Therefore I set up the 2 Service Beans with a TransactionProxy.
This 2 Beans are included into a other bean which handles the method calls.
Also this Beans writes messages over a JMS message queue. Those messages are read from in another EJB.
In BEA everything runs fine, I have the full transaction control over the 2 Service Beans and the JMS Messages can be read from the queue.
In the IBM environment it seems that the JMS Queue is also Part of the global Transaction. Should mean the beans in the second EJB which read from the queue do only recieve data if the global transaction is committed.
For me there are 2 questions:
1. Why does Websphere have this behaviour?
2. How can I manage it to receive always the messages?
thx for your advice