cancel
Showing results for 
Search instead for 
Did you mean: 

Endless loop in activiti with boundary-event miss-spelled

franz1
Champ in-the-making
Champ in-the-making
Hello,

my problem was, that I had a typo in the definition of the error at the boundary-event of the calling process

<boundaryEvent attachedToRef="calling"
cancelActivity="true" id="callingError">
<errorEventDefinition errorRef="someTypo" />
</boundaryEvent>

This led to an endless loop in ErrorEndEventActivityBehavior.executeCatchInSuperProcess(ActivityExecution)

while (!found && outgoingExecution != null) {

if (outgoingExecution != null && catchingActivity != null) {

}
}

as after one iteration I had found=false, outgoingExecution!=null, catchingActivity=null

It would be desirable to get an exception in this case. If I hadn't had this running in the debugger, I'd probably still searching for that error 😞

Thanks and regards


Franz
3 REPLIES 3

jbarrez
Star Contributor
Star Contributor
That is most certainly a bug then. Strange it can be deployed.

Can you create a simple test case demonstrating the problem?

franz1
Champ in-the-making
Champ in-the-making
Sorry, it's still on my toDo-list 😞

Franz

bernd_ruecker
Champ in-the-making
Champ in-the-making
Just a side node, this problem was reported with http://jira.codehaus.org/browse/ACT-832 and is fixed in the meanwhile, since we improved error event handling in the engine.

Cheers
Bernd