Thanks for the reply Ashwin, I've read the Websphere docs and its pretty much a simple case of checking the checkbox 'Support distributed two-phase commit protocol' to enable XA-transactions. This is what we have. Our existing software which doesnt use camel or spring and uses EJB's works fine with JNDI. Ill try some other scenarios.
On 6 July 2011 18:30, Ashwin Karpe [via Camel] < [email protected]> wrote: > Hi, > > While I am no expert on Websphere, I believe, based n the behavior you have > noted, that transactional behavior is incorrectly set on the connection > factory in Websphere. > > Transacation rollback or NACK needs to be propagated by the connection back > to the broker which either restores the message back on the queue after > updating the retry count. Looks like the connection is not doing so or is > not configured to do so. > > Hence the broker gets rid of its copy and the message is lost. > > Cheers, > > Ashwin... > --------------------------------------------------------- > Ashwin Karpe > Apache Camel Committer & Sr Principal Consultant > FUSESource (a Progress Software Corporation subsidiary) > http://fusesource.com > > Blog:http://opensourceknowledge.blogspot.com > --------------------------------------------------------- > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/XA-transactions-with-JNDI-defined-JMS-connection-factories-tp4557202p4557477.html > To unsubscribe from XA transactions with JNDI defined JMS connection > factories, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4557202&code=Y2pydWZmeUBnbWFpbC5jb218NDU1NzIwMnwtNDIzNDY3OTA4>. > > -- View this message in context: http://camel.465427.n5.nabble.com/XA-transactions-with-JNDI-defined-JMS-connection-factories-tp4557202p4560388.html Sent from the Camel - Users mailing list archive at Nabble.com.
