You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Raul Montes (JIRA)" <de...@tapestry.apache.org> on 2008/06/11 20:22:45 UTC
[jira] Created: (TAPESTRY-2454) tapestry-hibernate transaction
management doesn't work as expected when commiting more than once on the
same request
tapestry-hibernate transaction management doesn't work as expected when commiting more than once on the same request
--------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2454
URL: https://issues.apache.org/jira/browse/TAPESTRY-2454
Project: Tapestry
Issue Type: Bug
Components: tapestry-hibernate
Affects Versions: 5.0.12
Environment: Mac OS 10.5.3, Jetty 5.1.14, MySQL 5.1, Hibernate 3.2.6GA
Reporter: Raul Montes
Inside a request (and then on the same hibernate Session), after a first commit, the second transaction works "partially" (some operations won't persist).
Apparently, this is because the method HibernateSessionManager.commit does a commit on the transaction it obtains from Session.beginTransaction (when first creating the Session) and then it calls begin() on the same Transaction, which apparently isn't the real underlying transaction on the database.
If this is true, the solution could be get the underlying transaction again after committing either calling Session.getTransaction and Transaction.begin or just Session.beginTransaction.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-2454) tapestry-hibernate transaction
management doesn't work as expected when commiting more than once on the
same request
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-2454:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> tapestry-hibernate transaction management doesn't work as expected when commiting more than once on the same request
> --------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2454
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2454
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.0.12
> Environment: Mac OS 10.5.3, Jetty 5.1.14, MySQL 5.1, Hibernate 3.2.6GA
> Reporter: Raul Montes
> Assignee: Howard M. Lewis Ship
>
> Inside a request (and then on the same hibernate Session), after a first commit, the second transaction works "partially" (some operations won't persist).
> Apparently, this is because the method HibernateSessionManager.commit does a commit on the transaction it obtains from Session.beginTransaction (when first creating the Session) and then it calls begin() on the same Transaction, which apparently isn't the real underlying transaction on the database.
> If this is true, the solution could be get the underlying transaction again after committing either calling Session.getTransaction and Transaction.begin or just Session.beginTransaction.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2454) tapestry-hibernate transaction
management doesn't work as expected when commiting more than once on the
same request
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604355#action_12604355 ]
Howard M. Lewis Ship commented on TAPESTRY-2454:
------------------------------------------------
See also http://forum.hibernate.org/viewtopic.php?p=2387715#2387715
> tapestry-hibernate transaction management doesn't work as expected when commiting more than once on the same request
> --------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2454
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2454
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.0.12
> Environment: Mac OS 10.5.3, Jetty 5.1.14, MySQL 5.1, Hibernate 3.2.6GA
> Reporter: Raul Montes
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.14
>
>
> Inside a request (and then on the same hibernate Session), after a first commit, the second transaction works "partially" (some operations won't persist).
> Apparently, this is because the method HibernateSessionManager.commit does a commit on the transaction it obtains from Session.beginTransaction (when first creating the Session) and then it calls begin() on the same Transaction, which apparently isn't the real underlying transaction on the database.
> If this is true, the solution could be get the underlying transaction again after committing either calling Session.getTransaction and Transaction.begin or just Session.beginTransaction.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-2454) tapestry-hibernate transaction
management doesn't work as expected when commiting more than once on the
same request
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2454.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.14
> tapestry-hibernate transaction management doesn't work as expected when commiting more than once on the same request
> --------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2454
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2454
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.0.12
> Environment: Mac OS 10.5.3, Jetty 5.1.14, MySQL 5.1, Hibernate 3.2.6GA
> Reporter: Raul Montes
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.14
>
>
> Inside a request (and then on the same hibernate Session), after a first commit, the second transaction works "partially" (some operations won't persist).
> Apparently, this is because the method HibernateSessionManager.commit does a commit on the transaction it obtains from Session.beginTransaction (when first creating the Session) and then it calls begin() on the same Transaction, which apparently isn't the real underlying transaction on the database.
> If this is true, the solution could be get the underlying transaction again after committing either calling Session.getTransaction and Transaction.begin or just Session.beginTransaction.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org