You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Aaron Hamid (JIRA)" <ji...@apache.org> on 2011/05/17 00:03:47 UTC
[jira] [Created] (DBCP-361) BasicManagedDataSource optional
transaction enlistment
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DBCP-361) BasicManagedDataSource optional
transaction enlistment
Posted by "Aaron Hamid (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034367#comment-13034367 ]
Aaron Hamid commented on DBCP-361:
----------------------------------
I don't know why Spring does not detect the existing transaction (both the platform tx manager and bmds are injected with the same (JOTM) tx manager), but it appears that this means BMDS won't work with Spring declarative transactions and PROPAGATION_REQUIRED (which is the default).
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DBCP-361) BasicManagedDataSource optional
transaction enlistment
Posted by "Phil Steitz (Updated) (JIRA)" <ji...@apache.org>.
[ 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