Possible hot hang in Singletrip traversal from GBS
When GBS 7.2 or above session is logged in to GemStone/S 64 Bit version
2.2.5 and above, under very specific circumstances a gem could hang consuming
CPU when responding to a request from GBS.
The circumstances require a graph of previously-replicated objects forming
a circular reference path, with a replication spec on one or more objects
with a combined minimum level sufficient to reach around the circular path.
If another previously-replicated object, not part of the circular path
but referencing an object in the circular path, was modified on the server
during the request from GBS, the gem would enter infinite recursion.
The immediate cause could be something otherwise innocuous such as an instance
variable update.
Workaround
Modifying the replication specs for involved objects to remove "min" settings
will avoid the problem.
Last updated: 7/1/10