I have a MDB forwarding messages to a Queue on a remote JBoss instance - how should the transaction management be configured on the MDB and the JMS RA?
Originally I had MDB with Container Managed Transaction using a JMS RA with NoTxnConnection Manager. Messages were being silently dropped. From stepping thru' the JBoss source that gets called to send the JMS message to the remote I noticed some code that seems to test the current transaction context and attempt to do some XA transaction related processessing even though the remote JMS service isn't an XACOnnection Manager - could there be a problem here wrt a Container Managed transactional MDB invoking a non-XA JMS RA?
I tried changing to using a JMS RA with an XACOnnectionManager - however it then threw an exception indicating that the remote JMS service could not participate in an XA transaction. So I changed the MDB to being Bean Managed (ie. no transaction) and then the behavior has gone back to silently dropping the message. (However I still see the code apparently going down XA paths...)
I am chasing the problem desribed in:
http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=forums/ there be a genuine JBoss/JMS problem in that one a transactional MDB's would not work properly with a non TxCM JMS RA?
If anyone has such a 'forwarding MDB' configuration working I would much appreciate knowing how it was achieved (JMS RA wise) including your transaction behavior configuration.
I am using JBoss 3.0.4.
rgds,
Paul Bandler
