Replicated Objects do not Expire

Topics: Developer Forum, Project Management Forum, User Forum
Jul 2, 2009 at 1:53 PM

When an object is replicated it's Expires property is not copied and thus never expires on the replicated server, is this a bug or by design?

Jul 2, 2009 at 3:16 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Sep 3, 2009 at 4:34 PM

This is due to the CacheExpire class removing the object from it's local cache only. (ExpireJob Method). I think this Method should issue a ServiceLogic.NetworkDistribution.Replicate(msg) call to queue a replication request to the replicationQueue so that the object is removed from all replicated servers.

Sep 3, 2009 at 4:44 PM

there is no need for replication because each server identifies it as expired.

Sep 3, 2009 at 5:43 PM
Edited Sep 3, 2009 at 5:44 PM

How? the Expire property value is not copied to the replicated message as i pointed out previously?