10:54 a.m.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://jira.jboss.org/jira/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.GA
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance API.
When I throw the Runtime exception the changes to the ORDERS entity bean (i.e. updating
the tracking number) rolls back. The problem is that the task instance change (i.e. ending
the task) does not rollback. It appears that jBPM is flushing its changes in another db
transaction. This seems like a bug since I would expect the ending of my task to also
rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:02 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://jira.jboss.org/jira/browse/JBSEAM-4512?page=com.atlassian.jira.pl...
]
Jason E commented on JBSEAM-4512:
---------------------------------
I am adding a stack trace below. This is the portion of the strack trace immediately
after my db transaction rolls back (i.e. one that rolls back ORDERS table changes).
Notice that a new db transaction starts then Seam's ManagedJbpmContext flushes the
jBPM changes (i.e. ends my task).
2009-12-11 15:55:54,359 WARN [org.jboss.seam.web.ExceptionFilter] running exception
handlers^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.contexts.Lifecycle] After request,
destroying contexts^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.util.Work] beginning transaction^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.transaction.UTTransaction] beginning JTA
transaction^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered
Synchronization^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.util.Work] committing transaction^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.transaction.UTTransaction] committing JTA
transaction^M
2009-12-11 15:55:54,359 DEBUG [org.jboss.seam.bpm.ManagedJbpmContext] flushing seam
managed jBPM context^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener]
processing flush-time cascades^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener]
dirty checking collections^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.engine.Collections] Collection found:
[org.jbpm.taskmgmt.exe.TaskInstance.v
ariableInstances#1], was: [org.jbpm.taskmgmt.exe.TaskInstance.variableInstances#1]
(initialized)^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.engine.Collections] Collection found:
[org.jbpm.taskmgmt.exe.TaskInstance.p
ooledActors#1], was: [org.jbpm.taskmgmt.exe.TaskInstance.pooledActors#1]
(uninitialized)^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.engine.Collections] Collection found:
[org.jbpm.taskmgmt.exe.TaskInstance.c
omments#1], was: [org.jbpm.taskmgmt.exe.TaskInstance.comments#1] (uninitialized)^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.engine.Collections] Collection found:
[org.jbpm.taskmgmt.exe.TaskMgmtInstan
ce.swimlaneInstances#1], was: [org.jbpm.taskmgmt.exe.TaskMgmtInstance.swimlaneInstances#1]
(uninitialized)^M
2009-12-11 15:55:54,359 DEBUG [org.hibernate.engine.Collections] Collection found:
[org.jbpm.taskmgmt.exe.TaskMgmtInstan
ce.taskInstances#1], was: [org.jbpm.taskmgmt.exe.TaskMgmtInstance.taskInstances#1]
(initialized)^M
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://jira.jboss.org/jira/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.GA
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:39 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://jira.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugin....
]
Aram Nigiyan commented on JBSEAM-4512:
--------------------------------------
In our application we also faced this problem. I searched in internet and found some
similar problems and they also haven't got any response/support.
http://www.seamframework.org/Community/SeamJBPMTransactions
http://seamframework.org/Community/JbpmTransactionRollbackProblem
Is this topic going to be reviewed by you?
..it looks like the seam project is dead, but nobody says about it so that not to put
everybody in a bad mood.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://jira.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.GA
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:15 p.m.
New subject: [JBoss JIRA] Assigned: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny reassigned JBSEAM-4512:
-------------------------------------
Assignee: Marek Novotny
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.GA
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:17 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4512:
----------------------------------
Fix Version/s: 2.2.1.Final
Affects Version/s: 2.2.1.CR2
2.2.0.CR1
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.2.1.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4512:
----------------------------------
Fix Version/s: 2.3.0.ALPHA
(was: 2.2.1.Final)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Stefano Zaccaria commented on JBSEAM-4512:
------------------------------------------
Hello to all,
comfort to me know that I'm not the only one having this problem ... but this does not
solve it ...
Have any of you at least an idea to workaround ?
Thanks in advance.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4512:
---------------------------------------
The issue is more like integration design issue between JBPM and SEAM. Seam obviously
handles transaction rollback correctly, but when Seam does roll back JBPM won't know
about it, because Seam is transactional and after he rolled back the affected transaction,
it then starts new one for ending Seam request lifecycle and cleaning up. Closing of JBPM
context is there and dirty operations are committed.
So there is a need to close JBPM context while Seam is doing rollback and a transaction is
marked as Rolling back. I have no workaround so far, only fix.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Stefano Zaccaria commented on JBSEAM-4512:
------------------------------------------
Hello Marek,
thanks for your fast reply. In this moment I'm investigating about this problem.
I've try this code in a ActionHandler Class, but until now I not have the roolback
work in both session ( session from seam and session from jbpm )...
{code:title=TestActionHandler.java|borderStyle=solid}
public class TestActionHandler implements ActionHandler {
private static final long serialVersionUID = 1L;
public void execute(ExecutionContext executionContext) throws Exception {
Log log = Logging.getLog(ControlloDocumento.class);
Session sessionjbpm = executionContext.getJbpmContext().getSession();
Session session = (Session)Component.getInstance("session");
log.info("Session take from jbpm : #0", sessionjbpm.hashCode());
log.info("Sessione take from seam: #0", session.hashCode());
Document doc = (Document)session.get(Document.class, 23l);
doc.setMessage("Write some data for test rollback... " );
throw new RuntimeException("Throw some exception for test");
// After the previous code the "message" property of doc entity save the
modify and not do the rollback !!!
}
}
{code}
Some idea to fix ?
Can help me? If you have time can contact you directly... I'm frustrated and shot down
:(
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4512:
----------------------------------
Fix Version/s: 2.3.0.Final
(was: 2.3.0.ALPHA)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Jason E commented on JBSEAM-4512:
---------------------------------
I am confused with latest comment. The bug still shows Open status and unresolved. But
fixed in 2.3.0.Final. If this version available for download? Is this an issue in Seam
3.0? Also, can you list which files were changed for this fix?
Thanks!
Jason
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4512:
---------------------------------------
Jason,
which comment do you mean? I have only rescheduled the issue to different version from
2.3.0.Alpha to 2.3.0.Final. There is no fix yet.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Jason E commented on JBSEAM-4512:
---------------------------------
Do you know if this problem exists in Seam 3.x?
Thanks!
Jason
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4512:
---------------------------------------
Well, there is Droolsjbpm integration module in Drools project.
https://github.com/droolsjbpm/droolsjbpm-integration
But Jbpm 5 integration is not done yet.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Jason E commented on JBSEAM-4512:
---------------------------------
I do not understand your response. This bug exists in Seam 2.x and will be tentatively be
fixed in Seam 2.3. But I wanted to know if this same bug exists in Seam 3.x. If it is
already fixed in Seam 3.x I will look at upgrading to that version.
Thanks!
Jason
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:40 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4512:
---------------------------------------
I understand your confusion, but Seam 3 is not the same as Seam 2. Seam3 is definitely
different programming model under Seam3. So it started based on CDI and Seam 3 modules are
extensions to CDI. While Seam 2 is integration framework. Seam 3 is more like
extension/integration of nonEE technologies with Java EE 6.
Therefore I wrote about Droolsjbpm-integration project. It is Drools team, which is doing
integration of Drools/Jbpm with CDI.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Fix For: 2.3.0.Final
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:43 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Pete Muir updated JBSEAM-4512:
------------------------------
Original Estimate: 3 days
Remaining Estimate: 3 days
Priority: Minor (was: Major)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Priority: Minor
Fix For: 2.3.0.Final
Original Estimate: 3 days
Remaining Estimate: 3 days
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Jason E commented on JBSEAM-4512:
---------------------------------
Will this fix make it into Seam 2.3? I noticed 2.3 is in beta currently.
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Priority: Minor
Fix For: 2.3.0.Final
Original Estimate: 3 days
Remaining Estimate: 3 days
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:56 a.m.
New subject: [JBoss JIRA] (JBSEAM-4512) BPM task does not rollback
[
https://issues.jboss.org/browse/JBSEAM-4512?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4512:
----------------------------------
Fix Version/s: The future
(was: 2.3.0.Final)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://issues.jboss.org/browse/JBSEAM-4512
Project: Seam 2
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.CR1, 2.2.0.GA, 2.2.1.CR2
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
Assignee: Marek Novotny
Priority: Minor
Fix For: The future
Original Estimate: 3 days
Remaining Estimate: 3 days
I have made a simple change to the ShipAction.java class in the dvdstore example that
ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti =
ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance
API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e.
updating the tracking number) rolls back. The problem is that the task instance change
(i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in
another db transaction. This seems like a bug since I would expect the ending of my task
to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so
it should be easy to reproduce.
Thanks!
Jason
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4501
days inactive
5461
days old
18 comments
7 participants
participants (7)
-
Aram Nigiyan (JIRA) -
Jason E (Commented) (JIRA)
-
Jason E (JIRA)
-
Marek Novotny (Commented) (JIRA)
-
Marek Novotny (JIRA)
-
Pete Muir (JIRA)
-
Stefano Zaccaria (JIRA)