Home » Search

About fix

191-200 of 200Refresh
Forum
0

Deadlock in Doctor

which is attached to this post. Build 2.4.4_13 includes an attempt to fix this deadlock. Thank you for this report. Fixed. Thanks. lwalkowski
Issue
0

Deadlock on Schema Update during Multithreading activity

A possible deadlock was detected when new types are registered during multithreading activity against ObjectDB. Until this issue is fixed, the recommended workaround is to complete registration ... can find managed classes automatically. Version 2.5.1 should fix this issue.
Forum
0

Deadlock problems solved - a suggestion

you for your suggestion. The deadlock problem was filed as an issue. Hopefully this will be fixed soon and then a workaround will not be required. Update: An attempt to fix the deadlock is included in
Forum
0

deadlock with newest version 2.4.4_16

. if you could advise that would be great. Dan   Thank you for this report. Build 2.4.4_17 should fix this deadlock ... to do so or not. A synchronized that was added in build 2.4.4_10 to fix another problem caused
Forum
0

Deploying objectdb.jar to karaf 4.0.7 seems to fail

that this version fixes the issue. Regards, Alex Thank you for reporting this issue and for confirming that the new versions fixes it. alexweirig
Forum
0

Detaching objects after JOIN FETCH

case. The problem was added to the issue tracking system and hopefully will be fixed soon. Update: The issue is fixed now. lwalkowski
Forum
0

Distinct Error

.java:627) ~[objectdb-2.2.8.jar:na] ... 49 common frames omitted   Appears this has been fixed in 2.2.8_06, I was only using 2.2.8_02 OK. Maybe it is related to some of the bugs that were fixed in the last builds. pedwards
Forum
0

Does ObjectDB support lazy loading?

. Please try build 09 that should fix this issue. In addition, you might want to enhance your entity ... )] if the classes are not enhanced. I am using objectdb-2.0-RC4_04. You are right, thank you for the report. Please check the new build that should fix it. FredrikB
Forum
0

Duplicate Entity class names causes Exception in Query

to run your test. Build 2.2.9_05 includes an attempt to fix the NullPointerException. The fix is based
Issue
0

Eager load Map

in eager fetch of collections and maps of simple values. Build 2.3.2_04 should fix this problem. Thanks - that fixed the test but unfortunately I still had the problem in the real application