hmm... this is such a low level issue that I'm not sure how to fix it.
What you should do is see on what tokens this happens and see if for that token and all related variables, the id's and all related fields (see the datamodel in the sticky post in this forum) etc contain wrong errors. This can be done by comparing to entries that are correct.
There is no database repair or 'check validity' script (unfortunately)
Thank you for your quick response. Somehow i am able to match the relations and tried correcting the missing relation (NULL values) and got the system stable.
But, I think it is necessary to have a validation routines/scripts (could be optional , can be enabled by configuration) to validate the process execution data before starting the actual work to reduce the problems in this kind of scenarios.
I am interested to work on this use case and shortly i will post the implementation considerations for this use case.
Could it be that the basic config of jBPM dit not use wel configured transactions?
If transactions (in your opinion) were configured correctly, please file a jira issue then for some validation software. Lets see what comes out. Please also describe your case (the cause, configuration etc) in it.
Being precise, here is our setup.
Jboss Seam 1.2.GA and
Tomohawk , myfaces
on jboss 4.0.5.GA along with mysql 5.0.24 on RHEL 4 update 4.
If i am wrong please correct me. Jboss seam transaction handling is not much fine grained to handle EJB3 transactions and JBPM transactions together in 1.2.X versions of Seam. But, i have read that it is better in Seam 2.X, but as we have seen that upgrading to newer version of Seam is not much easy at this point of time, we are still living with this kind of transactional issues.
Anyway, i'll prepare the testcases to demonstrate the issue eventhough it is bit difficult as in our implementation JBPM is tightly coupled with EJB3 model.
If you seem to have problems related to jBPM and Seam, you stand a better change of more detailed help in the seam forum. A combination of ejb3, jBPM and Seam 1.2 is not our (my) field of expertise.