tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Jung" <>
Subject Re: DeltaManager for Clustering
Date Fri, 29 Jul 2005 20:18:24 GMT
Hi Dennis,

assuming you have a valid cluster config you don't need to start/stop the
DeltaManager yourself.

Session attributes are only replicated, if they are serializable and the
changes to the attributes are applied via setAttribute. If your attribute
e.g. is a HashMap and you change an entry via getAttribute and then access
by a key, the cluster will not know about the change and not replicate the
new data. On the other hand this way you can obscure changes you don't
really need from the replication and save some replication load.

Is replication working in general in your setup?

> Is there documentation on using the DeltaManager for clustering?
> In the javadoc there is this statement:
> --CUT--
> Correct behavior of session storing and reloading depends upon external
> calls to the start() and stop() methods of this class at the correct
> times.
> --END--
> The tomcat clustering howto doesn't mention this though.  Are the
> start/stop calls referred to for the container, or does the user
> application have to do something?
> I have some objects in the session that are not being syncronized
> accross the cluster and am trying to figure out if I'm doing something
> wrong either in the config or in the code.
> Thanks
> Dennis
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message