[
https://issues.apache.org/jira/browse/DBCP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-361:
-----------------------------
Fix Version/s: 2.0
> BasicManagedDataSource optional transaction enlistment
> ------------------------------------------------------
>
> Key: DBCP-361
> URL: https://issues.apache.org/jira/browse/DBCP-361
> Project: Commons Dbcp
> Issue Type: New Feature
> Reporter: Aaron Hamid
> Fix For: 2.0
>
>
> It would be nice to not automatically enlist connections in a transaction. I
> have found automatic enlistment can be problematic when using another
> transaction API such as Spring's declarative transactions
> (JtaTransactionManager). It appears Spring may create a second, wrapping
> transaction. With Oracle this leads to: ORA-02089: COMMIT is not allowed in
> a subordinate session.
> E.g. see Bitronix setAutomaticEnlistingEnabled
> http://btm.codehaus.org/api/1.3.3/bitronix/tm/resource/common/ResourceBean.html#setAutomaticEnlistingEnabled(boolean)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
