hello again, just forgotten something... i tried the solution (signalling the subprocess so that the superprocess doesnt throw an exception) just by signalling the newest processInstance of the subprocessDefinition. in a test environment this is fine, but in a multiuser production environment the latest instance of a that process could as well have been created by another user just a moment later. but that would mean i have to get the processinstance from the processstate and there is only a method for getting the processDef. i hope i'n not completely on the wrong trail... again best regards gregor View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076842#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...