Issue #1207: Unexpected exception (Error 990)

Exception is thrown on commiting a transaction using this code:

transaction.begin();
try {
   repository.setStatus(ImportStatusFlag.RUNNING_IMPORT);
   repository.setImportProgressMessage("Importing..."); //$NON-NLS-1$
   repository.setImportProgressPercent(0);
   transaction.commit();
} finally {
   if (transaction.isActive()) {
      transaction.rollback();
   }
}

"repository" is a Entity in database. Stracktrace as follows:

[2013-08-21 11:54:27 #29 client]
[ObjectDB 2.5.1_02] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.7.0_25 (on Windows 8 6.2).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: null
com.objectdb.o.InternalException
at com.objectdb.o.TYM.an(TYM.java:724)
at com.objectdb.o.IXM.f(IXM.java:72)
at com.objectdb.o.URT.T(URT.java:131)
at com.objectdb.o.PPW.<init>(PPW.java:54)
at com.objectdb.o.UPT.C(UPT.java:129)
at com.objectdb.o.URT.l(URT.java:171)
at com.objectdb.o.TSK.i(TSK.java:146)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.TSM.e(TSM.java:87)
at com.objectdb.o.UTT.A(UTT.java:365)
at com.objectdb.o.UTT.l(UTT.java:203)
at com.objectdb.o.TSK.i(TSK.java:146)
at com.objectdb.o.TSK.f(TSK.java:95)
at com.objectdb.o.TSM.e(TSM.java:87)
at com.objectdb.o.MST.Vc(MST.java:1284)
at com.objectdb.o.WRA.Vc(WRA.java:372)
at com.objectdb.o.WSM.Vc(WSM.java:174)
at com.objectdb.o.STC.v(STC.java:514)
at com.objectdb.o.SHN.an(SHN.java:563)
at com.objectdb.o.SHN.K(SHN.java:170)
at com.objectdb.o.HND.run(HND.java:132)
at java.lang.Thread.run(Thread.java:662)

Thank you for this report.

The exception is thrown when the server (during commit) unexpectedly fails to locate a type in order to update an index.

Did you get this exception after changing the schema?

If the schema has changed, was the server restarted before using the new schema?

After restarting the server, do you still get this exception?

Thanks a lot for the fast reply. Restarting the objectdb server indeed solved the exception.

Previously we only tried to restart the application server (Tomcat).