ObjectDB Database Search

: During sudden events of socket creations, information on the new sockets should be written to the ObjectDB

After updating some of my code to java 8, enhancement threw "unexpected" exceptions from two of the source files I applied the most (maybe all) of the changes to. Problem might or might not have been related to the java 8 update. In any event , my enhancement problem went away when I

event callbacks. ObjectDB should produce better error messages, but if the same code works outside

JDO's Unique annotation . For other constraints you can check objects in lifecycle events . support

of events was: 13:20 - our monitoring reported GC time per minute on the SLAVE instance over 30

- one with mapped by, second with adding entities list without "mapped by". The difference is huge event

I have an application which runs correctly in NetbeansIDE but after building it, it won't just run sometime, the app stop responding to event at a particular point. I was able to reproduce this issue while running the jar file in command line and I got this exception which I have it stack attached

(Timer.java:244) at java.awt. event .InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt

(SAXParserImpl.java:333) at ch.qos.logback.core.joran. event .SaxEventRecorder.recordEvents(SaxEventRecorder.java

Hello, we get into a deadlock, if two threads  try to close an entity manager. The first thread try to close the entity manager factory which close all opened entity managers. The second thread is triggered by an event and try to close the entity manager after a database access. Both threads

is also thrown for the following simpler query: SELECT e FROM Event e WHERE TYPE(e) = Practice AND ((Practice