About report

issue

InternalException in Database Doctor

Database Doctor has thrown an InternalException right after starting to diagnose or repair my DB file. The version of the Doctor used was 2.6.9_06. The stacktrace below:   ... Server VM 1.8.0_111 (on Linux 4.4.0-45-generic). Please report this error on ... so it should solve the exception. Thank you for your report. ObjectDB Support ObjectDB - Fast Object ...

 
issue

NPE using AND TRUE in WHERE clause

The following (dynamically generated) query causes an NPE: SELECT e FROM Event e WHERE e.account=:account AND TRUE When I change it to a trivial term which evaluates to true, it works fine: SELECT e FROM Event e WHERE e.account=:account AND 1=1 Here is the stack trace: ... 64-Bit Server VM 1.6.0_32 (on Windows 7 6.1). Please report this error on ... Thank you for this report. Build 2.5.1_02 fixes this issue. ObjectDB ...

 
issue

Query execution causes an unexpected internal exception (Error 990)

We have the following exception, why our query fails? ... 64-Bit Server VM 1.8.0_51 (on Windows 7 6.1). Please report this error on http://www.objectdb.com/database/issue/new ... database with the ObjectDB Doctor, and post the result report. ObjectDB Support ObjectDB - Fast Object ...

 
issue

Exception on query

[2014-02-14 11:38:47 #1 *] [ObjectDB 2.5.4] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.7.0_17 (on Windows 7 6.1). 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.InternalException.f(InternalException.java:236) at com.objectdb.o.STA.K(STA.java:339) at com.objectdb.o.ENT.E(ENT.java:533) at com.objectdb.o.ENT.N(ENT.java:681) at com.objectdb.o.LDR.F(LDR.java:593) at com.objectdb.o.LDR.E(LDR.java:470) at ... 64-Bit Server VM 1.7.0_17 (on Windows 7 6.1). Please report this error on ... Thank you for your report. It will be merged with  issue #187 , which according to the ...

 
issue

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:   ... 64-Bit Server VM 1.7.0_25 (on Windows 8 6.2). Please report this error on ... Thank you for this report. The exception is thrown when the server (during commit ) ...

 
issue

Update query bug

Some code. Problem in UPDATE query.   ... HotSpot(TM) Client VM 1.7.0_07 (on Windows 7 6.1). Please report this error on ... to setting values not collections. Following your report the exception in this case was fixed with a meaningful error ...

 
issue

GC overhead limit exceeded

I had some memory problems with a process running over the weekend and received the following exceptions in the objectdb log: 1) ... 64-Bit Server VM 1.6.0_26 (on Windows 2003 5.2). Please report this error on ... 64-Bit Server VM 1.6.0_26 (on Windows 2003 5.2). Please report this error on ...

 
forum_thread

Unexpected exception (Error 990)

I have a huge amount of inserts/updates and after a about 850.000 Entities I got the following error:   ... 64-Bit Server VM 1.6.0_30 (on Windows 7 6.1). Please report this error on ... 14:01 This report was moved to the online  issue tracking  system. ...

 
forum_thread

DB Doctor sets type to "unknown" for new fields

Hi, we are using ObjectDB 2.5.4_04 on Linux. We added two new Boolean fields to a persistable type and run DB Doctor on the exiting DB file in order to update the schema. The fields are added to the schema as expected, however their type is set to unknown - we were expecting Boolean. The attached DB file is what was produced by DB Doctor after adding the emergency and broadcast fields. If you run in DB Explorer ... the new Boolean fields look fine. Apparently your report indicates an Explorer behavior of specifying null results as Unknown ...

 
issue

InternalException

  ... Client VM 1.6.0_25 (on Linux 2.6.32.12). Please report this error on ... Thank you for this report. The stack trace indicates an unexpected state during query ...