Posted: Mon Jul 14, 2008 11:22 am Post subject: XA question
Apprentice
Joined: 15 Aug 2006 Posts: 30
Hi fjb_saper,
I'm just reading this this thread as it is very similar to a problem I am pondering over at the moment.
I know having two JMS sessions is not recommended but suppose two sessions were created, is there any possible way to manage transactionality between those two sessions? Maybe by setting the Queue Manager as a XA Resource Manager?
a) Don't hijack the thread. Create a new one and if need be reference the other one.
b) Proper XA transactionality would need a proper J2EE transaction manager and preferably WAS. This would then bind both resources correctly in an XA transaction.
If no TM is available you can always try the single phase commit with an embedded schema: the resource enrolled first is the resource committed / rollbacked last....
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum