Hello, We noticed that the Timeout for XA Transactions is hardcoded in the JDBC Drivers to 30seconds. The drivers dont try to make this configurable or try to correlate it with the actual transaction timeouts of the physical connections. I wonder if there is a reason for this. It seems to be the ame for 7.5 and 7.6.
I have a patch which will add a new configuration property to the XADataSource (which is then passed to the XAConnection). Are there any plans here, so we dont need to compile and ship the drivers ourself? We do use distributed transactions in app servers to have the JMS Provider and the CMP provider inside the one single global transaction. Some of those work items require more time to complete than the enforced 30 seconds. Greetings Bernd Eckenfels Chief Architect -- http://www.seeburger.com
