[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2309) UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
by Denis Forveille (JIRA)
UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2309
URL: http://jira.jboss.com/jira/browse/JBSEAM-2309
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.GA, 1.2.1.GA
Reporter: Denis Forveille
In the org.jboss.seam.util.Work class, the call to userTransaction.commit() is surrounded by a try/catch(Exception). In the catch block, if an exception occurs during the commit, a UserTransaction.rollback() is attempted. This may fail as the UserTransaction.commit() may throw a RollbackException, and in that case the UserTransaction ihas already been rollbacked. So an attempt to perform a rollback on the UserTransaction result in an illegalstate exception. This happens to us when something goes wrong in the beforeCommit() methods and hibernate throws a StaleObjectStateException()
We use seam 1.2.1 + POJO + WebSphere v61.0..13
The code could be something like this (Class Work.java):
try {
T result = work();
if (begin) {
log.debug("committing transaction");
userTransaction.commit();
}
return result;
} catch (Exception e) {
if (begin) {
log.debug("rolling back transaction");
if (userTransaction.getStatus() != STATUS_NO_TRANSACTION) {
userTransaction.rollback();
}
}
throw e;
}
Or the code could explicitely catch the RollbackException
This could be applied at any place in the code when a UserTransaction.commit() is called.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-884) ICEFaces dataPaginator causes duplicate ID exception
by henrik lindberg (JIRA)
ICEFaces dataPaginator causes duplicate ID exception
----------------------------------------------------
Key: JBSEAM-884
URL: http://jira.jboss.com/jira/browse/JBSEAM-884
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.1.6.GA
Environment: Seam 1.1.6.GA, ICEFaces 1.5.3
Reporter: henrik lindberg
Assigned To: Gregory Dick
Priority: Critical
When using a data paginator with a data table duplicate ids are created for all paginator facets except the first added facet.
The attached code illustrates the problem. Use the facelet to add test data, a duplicate id exception is thrown when a new test data is added.
Refresh the page (using browser) to see that data was added, try to add another (refresh again).
Editing out all facets for the paginator except one makes the code work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months