Incorrect connectors for String classes
In GBS releases earlier than 7.3, GBS used the Locale's stream encoder
to determine what client class to map to the server ISOLatin class. This
encountered problems in some OS environments due to changes in VW 7.6;
see bug #38785.
The fix for this bug was to always map the server ISOLatin class to a new
GBS class, GemStone.Gbs.ISOLatin class. However, this results in no mapping
for MSCP1252String or ISO8859L1String. If instances of these client specific
Strings are created, such as by reading a file, replicating them to the
server resulted in errors.
Workaround
Remove the connector from GemStone.Gbs.ISOLatin to ISOLatin. Create a
connector from MSCP1252String to ISOLatin (on Windows) or ISO8859L1String
to ISOLatin (on Unix).
Last updated: 2/25/10