You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2009/11/13 22:50:39 UTC
[jira] Closed: (OPENEJB-1109) Deploy time java.sql.SQLException:
Auto-commit can not be set while enrolled in a transaction
[ https://issues.apache.org/jira/browse/OPENEJB-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-1109.
----------------------------------
Resolution: Fixed
Bean in question now uses Bean-Managed Transactions
> Deploy time java.sql.SQLException: Auto-commit can not be set while enrolled in a transaction
> ---------------------------------------------------------------------------------------------
>
> Key: OPENEJB-1109
> URL: https://issues.apache.org/jira/browse/OPENEJB-1109
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: 3.0, 3.1, 3.1.1, 3.1.2
> Reporter: David Blevins
> Assignee: David Blevins
> Fix For: 3.1.3
>
>
> The DeployerEjb started a transaction as a side effect of it being an EJB. This led to oddities as the entire deploy process for that archive would execute in transaction. At deployment JPA PersistenceProviders will initialize and @Singleton beans may start. These should not be running in a transaction unless they themselves wish to start one.
> One particular reported issue involves Hibernate not being able to execute it's DDL updating logic (hibernate.hbm2ddl.auto) when the app is deployed. The resulting exception in this case is a deploy time exception like the following:
> java.sql.SQLException: Auto-commit can not be set while enrolled in a transaction
> Note, putting the application in the apps/ directory manually and restarting the server is one way to work around this issue in existing releases of OpenEJB.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.