[
https://issues.apache.org/jira/browse/GERONIMO-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-2576:
-----------------------------------
Priority: Major (was: Blocker)
> Rollbacks at database level throws exception in Geronimo
> --------------------------------------------------------
>
> Key: GERONIMO-2576
> URL: https://issues.apache.org/jira/browse/GERONIMO-2576
> 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: src.zip
>
>
> 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:- com.ibm.db2.jcc.c.SqlException: [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? I have created an example scenario
> and attached the source with this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
