This content has been marked as final. Show 2 replies
Hi,XA drivers are required if you have more than one database involved in the transaction, but in this case there's only one. I have to admit that I haven't tried queue and database in the transaction with both non-XA and XA to see if it made a difference.
Can i ask a question related to JMS.
I have a project where one of the requirement is that
a message when picked up from MQ > BEA JMS > and then
persistet into Database needs to be guaranteed i.e
either should be rolled back or commited.
My questions were:
1) is running the connection factory in XA is the
[The reason being, we have had lot of production
problems while running some of our application in JMS
XA mode and if possible, we wanted to use non-xa]
2) is the requirement to have "sequencing" needs toThe MQ-to-JMS bridge is another unknown to me. When you roll the database back, you expect to see the message put back on the MQ queue, right? Another unknown to me.
have XA on BEA JMS Bridge (between BEA > MQ) OR we
can accomplish "Sequencing" w/o been in XA Tx. ?
Iam just trying to learn this JMS stuff and if iamNot stupid at all. I would consider these to be rather advanced questions.
asking some stupid question, please do not get
offended and ignore my email.
I'm pretty sure that Spring's declarative transactions can handle this. Database POJO and MDP can participate in a single transaction.
The MQ wrinkle is unknown.
Sorry that I'm not more helpful here.