[jboss-jira] [JBoss JIRA] Commented: (JBTM-93) Oracle setTransactionTimeout only propagates to server during XAResource.start method invocation
[ http://jira.jboss.com/jira/browse/JBTM-93?page=comments#action_12339734 ]
Kevin Conner commented on JBTM-93:
----------------------------------
The order of the method invocations has been swapped and the setTransactionTimeout is now
configurable.
There are two ways to configure this functionality
- specify the com.arjuna.ats.jta.xaTransactionTimeoutEnabled property (defaults to true)
- programmatically using the setXATransactionTimeoutEnabled method on
com.arjuna.ats.jta.common.Configuration
(Boolean.TRUE/enabled, Boolean.FALSE/disabled, null/use property value)
Oracle setTransactionTimeout only propagates to server during
XAResource.start method invocation
------------------------------------------------------------------------------------------------
Key: JBTM-93
URL: http://jira.jboss.com/jira/browse/JBTM-93
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation, JTS Implementation
Affects Versions: 4.2
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.1
Invocations of the XAResource.setTransactionTimeout method are cached by the Oracle
driver until a call to the XAResource.start method has occurred.
The Type 4 driver accepts the new value and stores it locally but this does not appear to
be propagated except as part of the start method invocation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira