I cant answer for sure. As I said, my experience with clustering is
limited, although the only problem we had was specifically with the SSO
data. Once I extended ClusterSSO to automatically request all known SSO
data from the cluster, the problem went away.
On Thu, Sep 3, 2009 at 9:57 PM,
Can anyone help in these regards?
Thanks in advance,
Sumedh
On Thu, Sep 3, 2009 at 8:52 AM, Sumedh Sakdeo sumedhsak...@gmail.comwrote:
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
*How it Works
*
1. TomcatA starts up
2. TomcatB starts up (Wait that TomcatA start is
Hello All,
I have a setup with two tomcat instances(AB). I have configured
an apache web server 2.2 for load balancing and fail over. Setup looks fine
as per the configurations suggested. Let tomcat A be handling some request
at sometime. When tomcat instance(A) goes down, the session
On 02.09.2009 19:57, Sumedh Sakdeo wrote:
Hello All,
I have a setup with two tomcat instances(AB). I have configured
an apache web server 2.2 for load balancing and fail over. Setup looks fine
as per the configurations suggested. Let tomcat A be handling some request
at sometime.
Hi Rainer,
I am using Tomcat session clustering and Apache Http Server for LB(using
mod_jk module). Also, using Tomcat 6. I have made appropriate changes to
worker.properties and httpd.conf. Also I have made appropriate changes to
server.xml on each tomcat.
Thanks,
Sumedh
On Thu, Sep 3, 2009
We had a similar problem with Tomcat 6 using clustering. It turns out that
the SSO information is only propagated while all instances are running. If
Instance-A fails, several users then log in to Instance-B, then Instance-A
comes back up, all of the SSO information for the users that logged in
After re-reading your initial post, the problems might not be as related as
I thought since at no point did replication stop for me.
On Thu, Sep 3, 2009 at 9:56 AM, Shaun Senecal ssenecal.w...@gmail.comwrote:
We had a similar problem with Tomcat 6 using clustering. It turns out that
the SSO
Shaun,
Yes we have a user session object created when user logs on with proper
credentails.
For ex: At startup of two servers lets say user A has logged in.
As you are saying the SSO information is propagated while all instances are
running. So when for first time when tomcat which was handling
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
*How it Works
*
1. TomcatA starts up
2. TomcatB starts up (Wait that TomcatA start is complete)
3. TomcatA receives a request, a session S1 is created.
4. TomcatA crashes
5. TomcatB receives a request for session S1
6.
