Hey,
with the next tomcat 5.5.10 release you can add a ClusterListener and LifecycleListener to
your cluster config to realize those ServletContext attributes replication things. Look at the current cvs head
and test it.
<ClusterListener className="org.apache.catalina.cluster.session.ClusterSessionListener" />
<ClusterListener className="your class" />
<Listener className="your class" />
Your LifecycleListener receive the manager/context un/registration event. BEFORE_MANAGERREGISTER_EVENT AFTER_MANAGERREGISTER_EVENT BEFORE_MANAGERUNREGISTER_EVENT AFTER_MANAGERUNREGISTER_EVENT
ClusterListener are receive the messages. (look at ClusterSessionListener or JvmRouteSessionIDBinderListener) You must define your own ClusterMessage implementation (SessionMessageImpl or SessionIDMessage)
Your code contribution is very welcome :-)
Peter
Will Hartung schrieb:
From: "Joakim Ahl�n" <[EMAIL PROTECTED]>
Sent: Friday, April 22, 2005 5:54 AM
Hi!
We have a cluster of two tomcat 5.5.9-machines using session
replication. However, we also have data in application scope (set with
getServletContext().setAttribute(...)) which as far as i have found in
the docs, is not replicated.
You need a cluster aware caching solution. Session replication is more for failover and such.
Look at something like OSCache and its ilk to get the functionality that you need.
Regards,
Will Hartung ([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]
