"kukeltje" wrote : Ed,
|
| Will putting an async=true on the node realy force a commit? That has to be
documented well then (rollback
| 's further on in the process a rollback will not be possible then) This is
not a problem if the process has to wait for the return value of the async
message node.
|
Ronald,
Take a look at Node.enter():
anonymous wrote : // execute the node
| if (isAsync) {
| ExecuteNodeJob job = createAsyncContinuationJob(token);
| MessageService messageService = (MessageService)
Services.getCurrentService(Services.SERVICENAME_MESSAGE);
| messageService.send(job);
| token.lock(job.toString());
| } else {
| execute(executionContext);
| }
|
|
So yeah, I think it leads to a commit.
Unfortunately, as efip10 found out, there's a race condition between the commit
and the new job.
-Ed Staub
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064389#4064389
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064389
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
