- what database? Oracle 8?
- what appserver? Weblogic 6?
- what version of jBPM? 2.0?
btw, funny. Two batchupdate problems in one day hmmm.
Sorry for lack of clarity:
using Oracle 10g, Tomcat 5.5, jBPM 3.1.2
It's one of those errors that chains up to the Hibernate save so there's no code reference to point to.
Any pointers or ideas of where to start would be awesome.
I disabled the constraint to see if it was actually going to write the correct data and it was just the commit order as I suspected, or if the parent key was really not being saved. Turns out, the parent key (Task Instance) is not being saved or is actively being deleted during the save. (There are Log rows referencing a Task Instance that no longer exists.)
10g in rac mode?
no, single DB only (for now).