Preventing OnSessionEnd from firing for each instancein a cluster.

[donatavant]

Hi,

I have a clustered setup of three computers each with a cf server instance
configured in a round-robin cluster with J2EE session variables enabled to
replicate session data. I read some where that session replication only occurs
upon a request and there's no way to replicate data in the application scope.
I'm only pushing data to the servers and the data is being updated frequently.

My problem is that because I'm only pushing data to the servers, the servers
will have inconsistent data and each of them fires the OnSessionEnd function.
Is there any way I can guarantee that they all have the lastest version of data
and that only one of the servers fires the OnSessionEnd function? And if that
assigned server fails, have it failover to another server?

In the OnSessionEnd function I'm writing to the db, and I'm trying to avoid
have to write a stored procedure to filter the data to find the latest
timestamp for each session.

Any help would be appreciated.

Thanks,
Don

[BKBK]

In a cluster environment, I would, in any case, store the session variables in the database, relating it with the data if and where necessary. That way, there'll be no fear of inconsistency.