Logins hanging or invalid key type errors in large repositories
GBJ must transmit the values for GemStone oops to the Java client.
Oop values of 536870912 (.5 billion) and above are represented as
LargePositiveIntegers, which was not handled properly by the
traversal buffers in versions of GBJ prior to 2.0. Oop values of
2147483648 (2 billion) and above cannot be represented as a 4-byte
signed value, and the marshalling of these is not handled properly
in GBJ 2.x.
These problems results in two different error symptoms: hang on login
(with eventual stack overflow on the Smalltalk side), or invalid
key type errors in the java client.
You can test if you are close to the limit by executing
System _oopHighWaterMark
Workaround
Please contact Technical Support for the appropriate filein.
Last updated: 3/19/04