geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arunanthisivam Vimalathithen (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2576) Rollbacks at database level throws exception in Geronimo
Date Fri, 17 Nov 2006 05:55:40 GMT
     [ ]

Arunanthisivam Vimalathithen updated GERONIMO-2576:


This example will recreate the issue with DB2.

> Rollbacks at database level throws exception in Geronimo
> --------------------------------------------------------
>                 Key: GERONIMO-2576
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector
>    Affects Versions: 1.1.1
>         Environment: Windows XP, DB2
>            Reporter: Arunanthisivam Vimalathithen
>         Attachments:
> I have a stateless session EJB which accesses a DB2 datasource created using the tranql
generic connector. This uses the container managed transaction. I am also using the DB2 9.1
universal JDBC drivers. For methods dealing with datasource related operations I have set
sessionContext.setRollBackOnly() within the catch block of SQLException.
> This throws exceptions when there have to be rollbacks at the database level. For example
trying to insert a duplicate record throws the following exception:-
[ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed
when in auto-commit mode. 
> Is there any way to turn auto-commit off? 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message