Hi All,
I've come across some interesting scenarios with a clustered Tomcat6
environment and I'm wondering what the most common (or best) approach to
configuration would be.
Basically, in a 2 node cluster, with a front-end Apache Web Server using
mod_jk balancer (on availability, with
Hi Darren,
For our setup tomcat 6 is able to handle failover to healthy node
with proper session replication. I assume you have loaded load balancer
module, updated worker.properties, made cluster changes to server.xml of
tomcat 6. My problem is next step of yours.
that actually
mean in this case? Availability of Tomcat on a node, or the
availability of the service to respond to requests?
-Original Message-
From: Sumedh Sakdeo [mailto:sumedhsak...@gmail.com]
Sent: 08 September 2009 10:49
To: Tomcat Users List
Subject: Re: Tomcat 6 Clustering issue
Ya... I got that message when I stopped the tomcat ( it shuts down with a
warning )
4th step in below is the scenario is where I got that warning
1) Start tomcat 1
2) Start tomcat 2
3) create atleast once session on tomcat 1 and tomcat 2 by accessing the
web application
4) kill any
Hi,
I have a tomcat cluster ( with tomcat 1 and tomcat 2 ) with a hardware
load balancer infront. Session replication only works in some scenario and
does not in others. Here is the scenario where it works...
1) Start tomcat 1
2) access the web application ( session gets created in
this message
2008-11-20 17:08:29.999 [main] [INFO]
org.apache.coyote.http11.Http11Protocol - Stopping Coyote HTTP/1.1 on http-8080
tells us that you stopped the tomcat instance
Filip
rohit aman wrote:
Hi,
I have a tomcat cluster ( with tomcat 1 and tomcat 2 ) with a hardware
load
