-
15. Re: Failed to delete ProcessInstance due to foreign key cons
I tried using the latest mysql connector but same error.
Unfortunately , I cant upgrade to the 3.2.x version as I have customised the jbpm code and extended it some places to get things done..
I tried this
PD1 - Parent
PD2 - Child
Deploy PD2 and then PD1 - delete both works fine
Deploy PD2 and then PD1 - execute PD1 and PD2 from PD1 - getting this error.. -
16. Re: Failed to delete ProcessInstance due to foreign key cons
If you have customized it, you probably did this by checking out the source. I cannot imagine the differences to be so big that you cannot fairly easily update your version to the latest source. If so... I think you have to manually find differences in the source (with help from Jira maybe) that might explain why it does work with Martin and not with you. It is kind of difficult (besides not having the time) to help you find issues in "your version"
-
17. Re: Failed to delete ProcessInstance due to foreign key cons
Hmm..that is goin to be the only option I have..
@Martin
Did you try both the ways which I tried and you are still not getting any error or you tried to delete immediately after deploying? -
18. Re: Failed to delete ProcessInstance due to foreign key cons
by 'both ways', are you referring to this:
Deploy PD2 and then PD1 - delete both works fine
Deploy PD2 and then PD1 - execute PD1 and PD2 from PD1 - getting this error..
where the difference in the second way is that there are actually (ended) process instances? Other than that, you are calling GraphSession.deleteProcessDefinition(..) - or use the link in the jbpm-console - just as in the first case?