Recently, we upgraded from an old CDO version (R20170614-0227) to a new integration build (I20200410-0100).

First, I would like to thank the CDO team (Eike?) for the work. We are very happy with CDO, especially the new version.

After upgrading, our integration tests found some new potential issues which I would like to discuss.

1.) Occasional exception when updating the security realm. See attachment: stacktrace_1._securityrealm.txt. This happens only in rare cases. But the impact is quite severy for us: repeating the action with a new transaction also fails.

2.) Accessing a resource from a view shortly after a transaction created the resource. See attachment: stacktrace_2_cdoid.txt. The exception points to a CDOResourceFolder which contains the new resource. Maybe this is a problem on our side? Do we need to ensure a proper timeout between a commit and accessing the resource?

CDOCommitInfo info = tx.commit();
long commitTime = info.getTimeStamp();

otherLocalView.waitForUpdate(commitTime);

3.) Under heavy load, we sometimes see the this exception. See attachment: stacktrace_3_heavyload.txt.

4.) Potentially a false-positive exception? Occurs during heavy load, but seems to have no bad effect on our side. See: stacktrace_4_unknownvalue.txt