unless the session is primary, the last accessed time wont matter, when
the session becomes primary, the last access time gets set immediately.
Filip
Joseph Lam wrote:
Found that only when a replication is explicitly triggered by
set/removeAttribute(), the other nodes' session.getLastAccessedTime() will
be synchronized.
Joseph
On Thu, 24 Feb 2005, Joseph Lam wrote:
Hi,
It seems that in my 4-node cluster (TC 5.5.8), the
session.getLastAccessedTime() only returns the last accessed time in each
particular node only. Is this normal? How can I get the last accessed
time of a session across the whole cluster?
Regards,
Joseph Lam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
