-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen,
On 9/20/2011 3:18 AM, steffen.scheu...@fiducia.de wrote:
>> 1. You should look into using "template" workers.
> Yes, the configuration would be cleaner, but is it a functional
> problem?
No, but it allows people to more easily debug your con
effen
Christopher Schultz schrieb am 19.09.2011
17:47:39:
> Von: Christopher Schultz
> An: Tomcat Users List
> Datum: 19.09.2011 17:48
> Betreff: Re: mod_jk doesn`t distribute and failover on tomcat-error
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Steffe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen,
On 9/19/2011 4:49 AM, steffen.scheu...@fiducia.de wrote:
> If one out of 6 balanced Tomcat-Server, throws an
> OutOfMemory-Error, mod_jk doestn´t distribute any Reqeuest to the
> other Servers, until we restart the faultet Server or stop the
Hy André,
sorry its a typo in my posting. The real workers.properties ist correct.
Greets
Steffen
Von:André Warnier
An: Tomcat Users List
Datum: 19.09.2011 11:45
Betreff:Re: mod_jk doesn`t distribute and failover on tomcat-error
Hi.
steffen.scheu...@fiducia.de wrote
Hi.
steffen.scheu...@fiducia.de wrote:
...
workers.properties Configuration:
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=Server1,Server2,Server3,Server4,Server5,Server6,Server7,Server8
worker.loadbalancer.sticky_session=True
worker.loadbalancer.sticky_session_force=False
wo
Hello Users,
we have a problem in one of our environments.
If one out of 6 balanced Tomcat-Server, throws an OutOfMemory-Error, mod_jk
doestn´t distribute any Reqeuest to the other Servers, until we restart the
faultet Server or stop the Server via jkstatus.
Here is a sample of the mod_jk-Logfi
