Jul 30th, 2010, 08:28 AM
Flow execution ended unexpectedly - StepExecution can't already have an id assigned
We are running 4 flows parallely in a split and occasionally the job fails on "Flow execution ended unexpectedly.." with underlying exception - "StepExecution can't already have an id assigned".
Whenever this has occured, three flows ran successfully, it fails on the last one.
We are left with no option to re-run the job when this happens.
Is there a reason why this happens ?
Attached is the stacktrace..
Last edited by Nitty; Jul 31st, 2010 at 05:55 AM.
Aug 1st, 2010, 07:41 AM
Could you post some configuration for the job and steps?
Aug 2nd, 2010, 02:15 AM
Cancel that. I can see from the stacktrace that this is probably the end of an earlier topic on deadlocks (http://forum.springsource.org/showthread.php?t=86587). So there was a deadlock and the save operation is being retried? And it fails because the StepExecution id was set on the first try. If you confirm that is the problem we can look at solutions (it might be ugly).
Aug 10th, 2010, 11:47 AM
Yes it's related to previous thread and it may be due to the reason you mentioned.
Please find the job-config and the log (filtered by the error thread) attached.
Aug 11th, 2010, 01:58 AM
Is this a different job than the other thread (which seemed to work out OK)?
Can you add a check in your RepositoryInterceptor to reset the StepExecution id to null if the save fails and is going to be retried?