I never said you should remove async in your final version I just metioned it as one of the things to try in finding the cause. And that should be possible shouldn't it? Correct, the custom node class async but once it is finished it does nothing. If you want it to leave the node, you have to add execution.take(); If you do not want it to leave directly after it finished in the execute, add a execution.waitForSignal() and implement the signal(...) method. Again, see the examples. The way you do in now, your process is in an undefined state. And if in a unit test you manually execute the async jobs (see the examples again) you can check in what custom nodes the executions are in. That is how you should use unittests. The examples are very good for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254731#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...