Hey,
I have a question for any of you guru's out there. My colegues and
I are attempting to set up a load balanced apache-tomcat system. We are
attempting to configure the persistance manager in the server.xml
Because of the round robin scheduling of the webservers, every request
can theoretically go to either application server. Right now I am
getting some pretty strange behavior from the application. The way we
coded our servlets was to use a master base servlet to compare and
maintain session. The weird behavior is that even after you have logged
out and invalided the session. The persistance manager for some reason
resurrects the old deleted session when you log in again. The engine
issues a new session which dosen't match the old one and all hell breaks
loose with the app. The application we are using relies heavily on
session, and matching session ID's for security and storage of rather
large array's (vectors) of persistant data. Is anybody out their savy
enough to show me any kind of sample configuration that might help a
bit. I have already looked and used the sample configurations in the
Goodwill Apache-Jakarta book. They don't go very far in depth.
Thanks for any help in advance.
--
-----------------------------------------------
David J. Hladky [EMAIL PROTECTED]
Software Engineer
-----------------------------------------------
