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 --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/XA-transactions-with-JNDI-defined-JMS-connection-factories-tp4557202p4557477.html Sent from the Camel - Users mailing list archive at Nabble.com.
