We have solved the problem, in fact it seems that is not exactly slow
replication but slow deserialization of the sessiond data.
The way we solved this is not too good but deadlines. you know, if
at the first try we don get the session data we try again up to three
times spaced by 100ms
Hello.
We use tomcat 5.5.23.
We have had some problems when replicating what we have called
"sleeping session", that is: sessions different from the one that you
get if you ask the container for a session (by using
httpRequest.getSession()). What we did is to use the session we get
(we call it ca
