Home » Support » Issue Tracking » Exception in thread "ODB-StoreHandler-5094" java.lang.NullPointerException

Exception in thread "ODB-StoreHandler-5094" java.lang.NullPointerException

Type: BugVersion: 2.6.9Priority: NormalStatus: FixedReplies: 7
#1

Hi,

I am seeing hundreds of NullPointerExceptions being thrown from ObjectDb on our production server.  These are being written to a log by a server wrapper which runs ObjectDb as a service.  It looks like ObjectDb is not catching all Exceptions, allowing them to bubble up into the wrapper, which writes them to it's log file.  The stack traces do show that the Exceptions are originating from ODB code.  NullPointerExceptions are very concerning and we would like to ensure that no corruption is occurring in our data.  At the very least, it does appear that ODB read/write threads are terminating abnormally, I'm not sure how our application is reacting to these failures, as there are no timestamps that I can use for cross-referencing.

Can you please determine root cause of these Exceptions and identify why they are not showing up in the ODB log, and why they are bubbling up out of ObjectDb's code to the service wrapper?

Thanks,

Clinton Moore

813-562-0116

application/octet-stream iconservice.log (219KB)
service.log file with Exceptions from ObjectDb code
#2

What is the exact version/build number of ObjectDB that you use in production?

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

It seems that there is no risk of database corruption (although you may want to check the database with the ObjectDB Doctor to be on the safe side).

The exception is thrown by the ObjectDB server when a database connection is closed during cleanup of the closed connection. We will need the ObjectDB build number to get more information, as the line numbers in the stack trace do not match the most recent ObjectDB version. 

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#4

Hi,

The version of ODB that wrote the reported errors above is 2.6.9_4.

Thanks,

Clinton

#5

Apparently this issue has been fixed in version 2.7.0.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#6

What is happening when we hit the null pointer exception in a version prior to 2.7.0?  Are transactions failing and receiving a a JPA Persistence exception?  Is there any risk of database corruption or data loss?  We need to determine the urgency to upgrade ODB to a newer release.

 

Thanks,

Clinton

#7

There is no risk of database corruption at all.

The exception doesn't indicate a failed transaction but a failure of the server to cleanup a connection that apparently was opened but never used (no login). There may be some impact over time (but not necessaraly) on memory consumption and socket usage, but this could be negligible.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#8

Thank you.   Please close this ticket.

Clinton Moore


Post Reply

To post a reply and/or subscribe to update notifications - please login