WebSphere Application Server - Re: : Commit problem regarding XA transaction and JMS Default<br>

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > December 2006 > Re: : Commit problem regarding XA transaction and JMS Default<br>





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: : Commit problem regarding XA transaction and JMS Default<br>
David Currie

2006-12-07, 7:36 am

Hmm - nothing obvious immediately springs to mind. On the production
side it is running through the same code for each send i.e. using the
same connection factory and using the same logic for creating the JMS
artifacts? How about at the receiving end? Do you have one durable
subscription for each topic and all are created before the sending takes
place?

Regards,
David
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com