db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1004) Client should not require user to rollback the active transaction before call to PooledConnection.getConnection()
Date Thu, 08 Jun 2006 19:06:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1004?page=comments#action_12415409 ] 

Deepa Remesh commented on DERBY-1004:
-------------------------------------

Hi David, My comment was only based on your previous comment which made me wonder why you
did not add the rollback to resetConnection itself. Thanks for explaining your findings. As
I said before, the patch looks good and solves this issue.

> Client should not require user to rollback the active transaction before call to PooledConnection.getConnection()
> -----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1004
>          URL: http://issues.apache.org/jira/browse/DERBY-1004
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Versions: 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.1.2.3
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>     Priority: Minor
>  Attachments: DERBY-1004.diff
>
> For a PooledConnection.getConnection() the connection gets closed.
>  Embedded automatically rolls back any activity on the connection.
>  Client requires the user to rollback and gives an SQLException  
>  java.sql.Connection.close() requested while a transaction is in progress
> The test jdbcapi/checkDataSource.java shows this bug.   A boolean needRoolbackBeforePCGetConnection
has been added to the test and  explicit rollback has been added to the test to get it to
run with client.
> To reproduce take out instances of the explicit rollback for client from the test e.g.
> if (needRollbackBeforePCGetConnection)
> 			c1.rollback();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message