Hi Jacob,
Thanks for the reply.
My situation is a little more straightforward than the replication
cluster you are dealing with. In my case the first server is simply the
development environment and the second server is the production deployment
server. The two environments use identical OS and Tomcat so I am baffled at
why HttpSessionListener will only work on the server used for development.
Thanks
Randy
-----Original Message-----
From: Jacob Champlin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 8:51 AM
To: [email protected]
Subject: Re: HttpSessionListener
Randy,
I don't believe you have session replication set up in your cluster.
This is why when a session is created it only calls your
HttpSessionListener on one box. The second box will only get the
session if its replicated over to that box.
However! I tried to do the same thing and I was getting server lockups
when it a cluster. The HttpSessionListener would work fine on a single
box, but in a cluster both servers would lock up.
It is my belief that there is some concurrency issue in Tomcat/Session
Replication/HttpSessionListeners. However, I never found anything firm,
as is usually the case with concurrency issues.
Well I would love to hear if you get this working.
Jacob Champlin
EMO Corporation
---------------------------------------------------------------------
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]
