Hey,
manager is started after some other things are active.
s. Standardcontext.start() L.4079
WebApp Listener and Filters starts after manager. The
NamingContextListener (JNDI)
starts before Manager is started.
Ok, what can we do?
Peter
local-underground schrieb:
Peter,
Thanks for respon
Peter,
Thanks for response. I did not implement my own replication, I only looked at
the code
to see if my Context was started before the Cluster performed replication. Let
me try
and clarify by asking this question:
Does the Context start (meaning my servlet is started) before the Delta manag
Hey,
a) current tomcat 5.5.12 cluster implementation is a message
infrastructure.
b) The Context can used this message infrastructure to implement
remote session replication
c) When a Context start the DeltaManager sync with other nodes. That
means that all
sessions are transfered
Hello,
I am very curious why a Cluster does not make sure the context it is defined in
is
actually started before listening? This is proving to be a serious bug for me.
I am
implementing session replication where nested objects are defined via JNDI in
my context.
But when a new cluster membe
