I'm having trouble with the failover functionality of JK2. I have
apache connected to two back-end tomcat engines running on separate
machines. The failover works just fine when a tomcat engine dies.
The node is not given any requests and the webapp continues to
function normally. However, when
It seems as though my jk2 configuration isn't failing over properly.
If a tomcat machine drops, it compensates properly. However, if a
single application on one of the tomcat machines fails then apache/jk2
keeps that faulty app in the mix. When a user gets directed to a
tomcat instance where
Can either JK or JK2 properly failover when a webapp fails? They seem
to work fine when an entire tomcat instance drops, but they don't seem
to do anything useful when a single webapp on a tomcat instance breaks
down and starts throwing exceptions. They both continue to send
requests to the
I can't figure out, or find any documentation on how to map a uri in
workers2.properties to something other than its webapp directory name.
For instance, I want to make the directory
$CATALINA_BASE/webapps/mywebappv2.0.23 respond as though it were
$CATALINA_BASE/webapps/mywebapp. I'm certain
I have a rather strange problem. I have two RedHat machines running
Tomcat in a clustered arrangement. I am using the built in Cluster
element from tomcat 5.5.4. When idle, the machines seem to be working
fine. In fact, even under a slight load the machines perform well. I
can open up a
