You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Fischer (JIRA)" <ji...@apache.org> on 2006/05/01 18:35:46 UTC

[jira] Created: (TORQUE-12) serializable transactions using dbcp do not work in oracle

serializable transactions using dbcp do not work in oracle
----------------------------------------------------------

         Key: TORQUE-12
         URL: http://issues.apache.org/jira/browse/TORQUE-12
     Project: Torque
        Type: Bug

  Components: Runtime  
    Versions: 3.1, 3.1.1, 3.2    
 Environment: oracle
    Reporter: Thomas Fischer


Reported by raphael.x.mankin:

when connections are retrieved via SharedPoolDataSource and the transaction mode is set to serializable, e.g. by torque.dsfactory.bookstore.pool.defaultTransactionIsolation = 8, 
oracle exits with the error ORA-01453: SET TRANSACTION must be first in transaction when a sql command is issued




-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


[jira] Commented: (TORQUE-12) serializable transactions using dbcp do not work in oracle

Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/TORQUE-12?page=comments#action_12447256 ] 
            
Thomas Fischer commented on TORQUE-12:
--------------------------------------

Problem should be fixed in dbcp's svn; see https://issues.apache.org/jira/browse/DBCP-116

> serializable transactions using dbcp do not work in oracle
> ----------------------------------------------------------
>
>                 Key: TORQUE-12
>                 URL: http://issues.apache.org/jira/browse/TORQUE-12
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 3.2, 3.1.1, 3.1
>         Environment: oracle
>            Reporter: Thomas Fischer
>
> Reported by raphael.x.mankin:
> when connections are retrieved via SharedPoolDataSource and the transaction mode is set to serializable, e.g. by torque.dsfactory.bookstore.pool.defaultTransactionIsolation = 8, 
> oracle exits with the error ORA-01453: SET TRANSACTION must be first in transaction when a sql command is issued

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


[jira] Closed: (TORQUE-12) serializable transactions using dbcp do not work in oracle

Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TORQUE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Fischer closed TORQUE-12.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 3.3-RC3
         Assignee: Thomas Fischer

Problem is fixed in dbcp 1.2.2, which is used in 3.3-RC3

> serializable transactions using dbcp do not work in oracle
> ----------------------------------------------------------
>
>                 Key: TORQUE-12
>                 URL: https://issues.apache.org/jira/browse/TORQUE-12
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 3.1, 3.1.1, 3.2
>         Environment: oracle
>            Reporter: Thomas Fischer
>            Assignee: Thomas Fischer
>             Fix For: 3.3-RC3
>
>
> Reported by raphael.x.mankin:
> when connections are retrieved via SharedPoolDataSource and the transaction mode is set to serializable, e.g. by torque.dsfactory.bookstore.pool.defaultTransactionIsolation = 8, 
> oracle exits with the error ORA-01453: SET TRANSACTION must be first in transaction when a sql command is issued

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


[jira] Commented: (TORQUE-12) serializable transactions using dbcp do not work in oracle

Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/TORQUE-12?page=comments#action_12377241 ] 

Thomas Fischer commented on TORQUE-12:
--------------------------------------

I have verified the behaviour and suspect it is a bug in commons-dbcp-1.2.1.See http://issues.apache.org/bugzilla/show_bug.cgi?id=31811

This one is fixed in cvs repository.

However, I found another problem, see
http://issues.apache.org/bugzilla/show_bug.cgi?id=35591

I have submitted a patch to this against svn Revision 279315 of dbcp which should resolve the problem.
On building dbcp with the patch, a dbcp testcase fails, but it also fails without the patch.
I'd suggest to wait till dbcp releases a new snapshot (or even a release) and then iclude this snapshot.

> serializable transactions using dbcp do not work in oracle
> ----------------------------------------------------------
>
>          Key: TORQUE-12
>          URL: http://issues.apache.org/jira/browse/TORQUE-12
>      Project: Torque
>         Type: Bug

>   Components: Runtime
>     Versions: 3.1, 3.1.1, 3.2
>  Environment: oracle
>     Reporter: Thomas Fischer

>
> Reported by raphael.x.mankin:
> when connections are retrieved via SharedPoolDataSource and the transaction mode is set to serializable, e.g. by torque.dsfactory.bookstore.pool.defaultTransactionIsolation = 8, 
> oracle exits with the error ORA-01453: SET TRANSACTION must be first in transaction when a sql command is issued

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org