Bug 28208


6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4,,, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8,, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x,, 5.1.5, 5.1.4, earlier versions


#rtErrLostOtHandlingFailed while in a transaction

Under extreamly rare conditions, a gem that has just entered a transaction
will receive a LostOt signal sent from the stone while it was still outside
of a transaction.  The gem cannot properly handle the LostOt signal under
these conditions and will fail with a #rtErrLostOtHandlingFailed error
(GemStone error 2380).

If this error occurs at the end of a MarkForCollection, it is usually
benign.  You can check statmonitor/VSD data and GcGem logs to determine
if the MFC completed successfully or not.


None.  You should treat this as a normal LostOt event, and in GBS, logout
and log back in to resynchronize the GBS caches.

Last updated: