Running multi-threaded access to an embedded database using JDO, I'm getting a deadlock in objectdb code. Thread dump attached.
Deadlock in objectdb code
Thank you for this report. The thread dump indicates a possible deadlock during initialization of new persistent schema. Could you please confirm that your application may have registered new persistent types when it happened?
Yes, that could have happened - some of the persistent types may be being introduced at that point in the code.
Is there a convenient way to introduce classes to objectdb at the start of a run, so they aren't first encountered later? Also, is there a logging option to follow schema changes during a run?
> Is there a convenient way to introduce classes to objectdb at the start of a run, so they aren't first encountered later?
You can introduce a class by:
You can also introduce all classes by:
but this will work only when ObjectDB can find managed classes automatically.
> Also, is there a logging option to follow schema changes during a run?
Basic type registration was added now in build 2.5.0_06.
To see registered types add to the configuration file:
<logger name="type.registry" level="info" />
or, use the "debug" level to get more information on the registered type.
Thank you for your fast and effective response to my issue - the new logging option should help solve things.