I think your decision is a wise one :)
You can help by opening a bugzilla issue (Enhancement) for this topic.
This way we will remember easier, when we start JK3.
Regards,
Rainer
James Masson wrote:
Hi Rainer,
thanks for the advice - I think we'll stick with the current
configuration, as pe
Hi Rainer,
thanks for the advice - I think we'll stick with the current
configuration, as people here seem to understand it quite well. I don't
really like the idea of having to custom tweak things like the time-outs
on connection pools, for every entry, just because we're trying to make
mod_jk d
No easy idea. At the moment, fail_on_status is only for workers, and not
for workers in mounts.
If you want to go the worker way, there are some simple tricks to not
make it to complicated:
- you can use the reference-attribute, to use worker templates. That way
each worker only needs to con
Hi list,
I have a fully working mod_jk High-Availability Tomcat environment at
the moment, and I'm looking to start catching web-app failures, as well
as Tomcat server failures.
At the moment, the service looks like this:
Two Alteon hardware load balancers
feeding
Two mod_jk apache servers
feed
