Hi,
I'm wondering if there is any documentation on use cases where JMS and
JDBC transactions are mixed without the use of XA transactions?
There's a lot to say for using XA when combining messaging and
database persistence, but there's also a lot against it. I think the
pro's for using XA are well understood, so I'll focus on the con's
that are obvious to me:
+ you'll need a reliable global transaction broker, which means the
money you'd be spending on the license of such a product could get you
a very nice brand new car.
+ setting up, deploying and maintaining a system that uses XA
transactions is non-trivial.
+ what database are you going to use? MaxDB? How well tested is its XA
support? If MaxDB is not sufficiently stable, the only option left is
Oracle. Another very nice brand new car.
It's not that I want to get XA deliverables for free, I only want to
understand if it's possible to setup two use cases with local JMS and
JDBC transactions: receive a message, process it and update the
database is the first one, send a message and update the database is
the second.
Thanks for your feedback
Kind regards
Steven Devijver
|
