[
https://issues.apache.org/jira/browse/DBCP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697573#action_12697573
]
Trenton D. Adams commented on DBCP-286:
---------------------------------------
Sorry for taking so long to get back to you. I almost forgot, as I received
the email notification on the weekend.
> What jdbc driver are you using
oracle 10.2.0.4.0
> Where exactly are you setting automcommit on the connection?
new PoolableConnectionFactory(
new DriverManagerConnectionFactory(url, user, password),
connectionPool, null,
"SELECT 'ping' FROM dual", false,
true, // auto commit
Connection.TRANSACTION_SERIALIZABLE, null, abandonedConfig);
Then other code will do
connection.setAutoCommit (false);
That certainly is odd, because there is a distinct behaviour change when I
specify 1.2.1 in my maven pom file, and then switch to 1.2.2. I haven't done a
whole lot of debugging, so maybe I'm reporting something other than problems
with connection rollbacks.
Basically what I am seeing is I create a record in the oracle database, using a
"single" connection outside of the pool. Then, I try to read that record back
in another section of code, which gets a new connection from the pool. The
connection from the pool is unable to see the record, which I presumed is
because the connection was not rolled back. When I do a rollback, the record
is then visible. Then, as the next test, I don't do a rollback, but switch to
1.2.1, and it also works.
Any ideas on how to identify this?
> DBCP does not rollback
> ----------------------
>
> Key: DBCP-286
> URL: https://issues.apache.org/jira/browse/DBCP-286
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: maven, gentoo linux, any java version
> Reporter: Trenton D. Adams
> Priority: Blocker
> Fix For: 1.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> DBCP 1.2.2 does not do connection rollbacks. Or, at least the one in maven 2
> repositories does not. I switched back to 1.2.1, and it works great.
> I asked about this back in 2005, and it was stated that it did. And, it
> does, up until 1.2.2
> http://mail-archives.apache.org/mod_mbox/commons-user/200504.mbox/<[email protected]>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
