Multiple 32-bit server sessions can get constraint violations
If GBS connects and disconnects rapidly to different 32-bit server sessions, while also doing simple GemStone operations such as opening a GemStone browser, constraint violation errors may be raised. This happens because of Symbol canonicalization problems for symbols that are used during replication clamp creation.
Workaround
Replace Symbol>>newGSObjectMappingInSession: with this definition:
newGSObjectMappingInSession: aGbsSession
^aGbsSession privateExecute: self printString
Last updated: 10/23/08