Neither CHANGE_SESSION_ID message nor SESSION_EXPIRED message set timestamp. If these messages are received during cluster sessions synchronization in DeltaManager startup, because the timestamp is not set, they are dropped. I made a patch that add timestamp for CHANGE_SESSION_ID and SESSION_EXPIRED message. Best Regards.
Created attachment 26461 [details] I made a patch.
Fixed in 7.0.x and will be in 7.0.6 onwards. Proposed for 6.0.x and 5.5.x
Fixed in 6.0.x and will be in 6.0.30 onwards.
Created attachment 26482 [details] Patch against tc5.5 Patch against tc5.5
Will be in 5.5.32