One of my customers is reporting this issue.
Strange part is that the EO on which it is reported is not being updated/deleted/inserted in this transaction...it might be involved in a read operation.
this error is in the postChanges method of the EO and for the STATUS_UNMODIFIED state of the EO.
how can I diagnose this error? and get more details from the customer? unfortunately this error is from the middle tier, so not very sure about the next steps.
This is one of the 1st times a customer has reported this error in this area since RTM
Attached the stack trace below, as mentioned above, there are no updates/deletes/additions on MextVersionsEOImpl in this trxn. Exception origin postChanges method
postChanges method for this EO is overridden to specially handle STATUS_NEW state, it's not a very fancy customization though.
Caused by: oracle.jbo.AlreadyLockedException: JBO-26030: Failed to lock the record, another user holds the lock.
at oracle.jbo.server.OracleSQLBuilderImpl.doEntitySelectForAltKey(OracleSQLBuilderImpl.java:1105)
at oracle.jbo.server.BaseSQLBuilderImpl.doEntitySelect(BaseSQLBuilderImpl.java:566)
at oracle.jbo.server.EntityImpl.doSelect(EntityImpl.java:8519)
at oracle.jbo.server.EntityImpl.lock(EntityImpl.java:6156)
at oracle.jbo.server.EntityImpl.beforePost(EntityImpl.java:6677)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:6873)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:3301)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:7024)
at oracle.sysman.sdkImpl.core.mext.model.entity.EmMextVersionsEOImpl.postChanges(EmMextVersionsEOImpl.java:2033)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:3301)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:3104)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2906)
a.applicationModule.MextAMImpl.applyMextAssocsToTarget(MextAMImpl.java:2789)
... 70 more
- Detail 0 ##
appreciate your inputs