[
https://issues.apache.org/jira/browse/DBCP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693838#action_12693838
]
Trenton D. Adams edited comment on DBCP-286 at 3/30/09 9:55 AM:
----------------------------------------------------------------
We turn autocommit off usually. In this case, it is turned off, which is why I
noticed this. I was trying to retrieve a record that had just been inserted,
but it wasn't showing up. So, a co-worker mentioned that I might be in a
transaction, which would prevent me from seeing the latest records. So, I knew
that there was no way that "I" was in the middle of a transaction. So, I
decided to do a rollback just after getting the connection, and it then worked.
Then i tried 1.2.1, to see if it worked, without my own rollback, and it did.
connectionPool.setTestOnBorrow(true);
connectionPool.setTestOnReturn(true);
test is SELECT 'ping' FROM dual
Oh, and autocommit is on by default, but turned off in each classes that gets a
connection.
-rw-r--r-- 1 trenta trenta 559366 Jul 17 2008 commons-collections-3.1.jar
-rw-r--r-- 1 trenta trenta 121757 Mar 27 15:43 commons-dbcp-1.2.2.jar
-rw-r--r-- 1 trenta trenta 42492 Jul 17 2008 commons-pool-1.2.jar
Java 1.4.2-03, which I assume is JDBC2
> I assume that what you are seeing is when a connection is returned with
> readonly=false, automcommit=false, no rollback is
> happening in 1.2.2. Correct?
Yes, that is what I am seeing.
was (Author: trent):
We turn autocommit off usually. In this case, it is turned off, which is
why I noticed this. I was trying to retrieve a record that had just been
inserted, but it wasn't showing up. So, a co-worker mentioned that I might be
in a transaction, which would prevent me from seeing the latest records. So, I
knew that there was no way that "I" was in the middle of a transaction. So, I
decided to do a rollback just after getting the connection, and it then worked.
Then i tried 1.2.1, to see if it worked, without my own rollback, and it did.
connectionPool.setTestOnBorrow(true);
connectionPool.setTestOnReturn(true);
Oh, and autocommit is on by default, but turned off in each classes that gets a
connection.
-rw-r--r-- 1 trenta trenta 559366 Jul 17 2008 commons-collections-3.1.jar
-rw-r--r-- 1 trenta trenta 121757 Mar 27 15:43 commons-dbcp-1.2.2.jar
-rw-r--r-- 1 trenta trenta 42492 Jul 17 2008 commons-pool-1.2.jar
Java 1.4.2-03, which I assume is JDBC2
SELECT 'ping' FROM dual
> I assume that what you are seeing is when a connection is returned with
> readonly=false, automcommit=false, no rollback is
> happening in 1.2.2. Correct?
Yes, that is what I am seeing.
> MAJOR, MAJOR, MAJOR 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
> 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/<425cb254.1020...@pandora.be>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
