Oracle.jbo.RowAlreadyDeletedException raised on EO impl with dead status.

Question

Any help with this will be greatly appreciated as this is affecting our live environment and as yet we have no fix.
I have 3 tables (for simplicity lets call them table A, B and C). I have 3 entity objects related by strong association EO_A, EO_B and EO_C. EO_C is the child of EO_B which is the child of EO_A - simple. I have a view object for each entity and the VO's are related by view links. I am experiencing the following problem :
I insert a row into VO_A and then call a procedure on the database to insert some rows into tables B and C. I post my changes on the transaction then re-query VO_A. I then update a row in VO_C (for a given VO_B master record) in the UI and the change is succssfully set on the EO. I then cancel the transaction using DBTransaction.rollback(). I receive the error :
oracle.jbo.AfterRollbackException: JBO-26102: An error occurred after rollback was performed.
When I start the transaction again, the first time a transaction attached to the same Application Module tries to post changes, I receive the error (where SrResourcesEOis EO_B):
oracle.jbo.RowAlreadyDeletedException: JBO-25019: Entity row of key oracle.jbo.Key[5264 ] not found in SrResourcesEO
I have found that this is because the transaction is trying a SELECT FOR UPDATE NOWAIT on a row in EO_B that was created and rolled back in the previous failed transaction ???
Debug log entry (where SrResourcesEO = EO_B) :
"OracleSQLBuilderImpl.doEntitySelect(565) Executing LOCK...SELECT SCHEDULE_RESOURCE_ID, SCHEDULE_ID, PERSON_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3, ATTRIBUTE4, ATTRIBUTE5, ATTRIBUTE6, ATTRIBUTE7, ATTRIBUTE8, ATTRIBUTE9, ATTRIBUTE10, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE FROM CPW_SR_RESOURCES SrResourcesEO WHERE SCHEDULE_RESOURCE_ID=:1 FOR UPDATE NOWAIT"
I cannot understand why this is as the AM was released in the previously failed attempt and this is a completely new transction.
The really scary thing is that once this happens it affects ALL users, not just the user who's session caused the error. The error persists until the web server is restarted. It's almost as if (although I'm sure this can't happen) the previous corrupt transaction listener is still lurking around and is trying to re-try the action it previously failed on when the transaction next posts changes.
Findings:
1) The same problem happens if I delete a record.
2) If I insert a new record to EO_C in the UI and rollback the transaction I do not get the error. The problem only occurs if I update or delete a record that was created by the procedure on the database.
3) If I do the same DML into table B and C via the entity objects EO_B and EO_C not via the DB procedure, I do not get the error when I rollback.
4) The original error (JBO-26102) is being raised in afterRollback() on the parent EO_B.
5) The subsequent error (JBO-25019) is being raised in lock() on the parent EO_B.
It appears that I am experiencing a similar issue mentiond by Steve Muench in the following thread.
Re: Internal error: Entity.afterRollback.status_dead   -- What does this mean?
The difference is that I am not using dual composition. I do not have one child with two owning parents, I have one child (EO_C) with one owning parent (EO_B).
I am using JDeveloper version 9.0.3.5 (I am constrained to this version as I am using it in an OA environment)
We are running BC4J 9.0.3.13
Any help greatly appreciated.

Answer 1

Ok, i found out why I am getting the error and the raised exception:
Before the commit, I am doing
row.setAttribute("Attribute",newVal);
That's why it raises the exception. I commented out that line and I'm getting no error anymore. But it does not commits the operation to the DB (i.e. no new row is added to the table). So, the same behaviour as the delete operation that I talked about in the 1st post.