Issue #895: InternalException

Hi,

3 Days before our rollout.. We've just got this when trying to commit persist of a bunch of entities into the DB

Caused by: com.objectdb.o._RollbackException: Failed to commit transaction:
at com.objectdb.o.JPE.g(JPE.java:89) [objectdb-2.4.0.jar:]
at com.objectdb.o.ERR.f(ERR.java:60) [objectdb-2.4.0.jar:]
at com.objectdb.o.OBC.onObjectDBError(OBC.java:1504) [objectdb-2.4.0.jar:]
at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279) [objectdb-2.4.0.jar:]
{..}
... 25 more
Caused by: com.objectdb.o.InternalException
at com.objectdb.o.TYM.am(TYM.java:713) [objectdb-2.4.0.jar:]
at com.objectdb.o.IXM.f(IXM.java:72) [objectdb-2.4.0.jar:]
at com.objectdb.o.URT.T(URT.java:131) [objectdb-2.4.0.jar:]
at com.objectdb.o.PPW.<init>(PPW.java:54) [objectdb-2.4.0.jar:]
at com.objectdb.o.UPT.C(UPT.java:129) [objectdb-2.4.0.jar:]
at com.objectdb.o.URT.l(URT.java:171) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSK.i(TSK.java:146) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSK.f(TSK.java:95) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSM.e(TSM.java:87) [objectdb-2.4.0.jar:]
at com.objectdb.o.UTT.z(UTT.java:365) [objectdb-2.4.0.jar:]
at com.objectdb.o.UTT.l(UTT.java:203) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSK.i(TSK.java:146) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSK.f(TSK.java:95) [objectdb-2.4.0.jar:]
at com.objectdb.o.TSM.e(TSM.java:87) [objectdb-2.4.0.jar:]
at com.objectdb.o.MST.Vb(MST.java:1299) [objectdb-2.4.0.jar:]
at com.objectdb.o.WRA.Vb(WRA.java:369) [objectdb-2.4.0.jar:]
at com.objectdb.o.WSM.Vb(WSM.java:174) [objectdb-2.4.0.jar:]
at com.objectdb.o.STC.v(STC.java:511) [objectdb-2.4.0.jar:]
at com.objectdb.o.SHN.an(SHN.java:563) [objectdb-2.4.0.jar:]
at com.objectdb.o.SHN.K(SHN.java:170) [objectdb-2.4.0.jar:]
at com.objectdb.o.HND.run(HND.java:133) [objectdb-2.4.0.jar:]
... 1 more

Have you changed the schema recently (e.g. added new persistent fields)?

Do you still get the exception after restarting the server?

Can you check the database with the Doctor and post the output?

This issue is closed due to missing details.

The exception may be the result of changing schema without restarting the database.