Bug: 39900

Impact:

Product:
GemStone/S

Versions:
6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.3, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.2, 6.2.1, 6.2, 6.1.6, 6.1.5, 6.1.4, 6.1.3, 6.1.2, 6.1.1, 6.1

Platform:
All

Fixed In:

Remote cross-platform MFC has risk of gem crash

Running a markForCollection (MFC) from a remote gem that is on a machine
with a different byte order than the stone, and therefore requires swizzle,
can result in a gem crash with a preceeding message in the log:

"ObjSupSwizzlePageGet error on page 16778280 oop 10944580 (message can
be ignored if no further problems)"

Byte swizzling is required when a remote gem is Windows or Linux, and the
stone on Solaris, AIX or HP (or vice versa).

Workaround:

Avoid running MFC from gems that are remote from the stone and on a machine
with a different byte ordering.