Markus,
Is the header name called "Authentication" ? If so, we had this exact
same issue a few years ago. The length of this HTTP header was too long for
mod_jk to process and the request was getting dropped. I think you might be
able to configure the packet size of mod_jk now to get around this
Still continuing to guess..
>
> This is about efficiency.
> If mod_jk had to do a DNS lookup each time it wants to send a packet to a
> backend Tomcat (or at least each time it wants to create a new connection to
> a backend Tomcat), that would be very inefficient.
>
> So, instead, mod_jk stores th
tart, the
> load balancing members must at least be able to be resolved to an IP
> address, otherwise mod_jk determines that there's really something wrong
> with the configuration, and won't even start ?
>
>
>
>
>
> Scott Bradshaw wrote:
>
>> /portal/*=
roeprties ?
>
> -Original Message-
> From: swbrads...@gmail.com [mailto:swbrads...@gmail.com] On Behalf Of
> Scott Bradshaw
> Sent: Wednesday, April 15, 2009 3:51 PM
> To: users@tomcat.apache.org
> Subject: JK 1.2.28 - load balancer worker fails on startup with one
> worker down
I apologize if this a silly question, but I can't figure it out! I've looked
over the documentation and I'm stumped.
I have 5 load balanced workers defined. I have them setup and configured
correctly.
workers.properties file (partial - not including all the individual workers)
---
