Carpentier Luc (Uniway) wrote:
Ok,
[Fri Jan 27 08:24:52 2006] [1532:3412] [error] mod_jk.c (1932): Could not
init service for worker=wlb
[Fri Jan 27 08:26:31 2006] [1532:3828] [debug] mod_jk.c (1761): Shmem
cleanup
This means that the service failed to initialize and child exited.
The service
that this is less compliant. So it's a pitty that this
does not work on my tomcat version.
Thanks for you help.
Luc
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Friday, January 27, 2006 9:54
To: Tomcat Users List
Subject: Re: tomcat 5.5.15 jk1.2.15 connector problem
Carpentier Luc (Uniway) wrote:
You are completely right!
The option that was causing the trouble was:
JkOptions -ForwardURICompat
Right, at least one ForwardURIxxx is required.
So...
JkOptions -ForwardURICompat +ForwardURIEscaped
should work, as well as:
JkOptions
List
Subject: Re: tomcat 5.5.15 jk1.2.15 connector problem apache 2.0.55
Carpentier Luc (Uniway) wrote:
You are completely right!
The option that was causing the trouble was:
JkOptions -ForwardURICompat
Right, at least one ForwardURIxxx is required.
So...
JkOptions
Carpentier Luc (Uniway) wrote:
I even found contradictory information.
In the docs it states that the workers should not be defined in the
workers.list when you are using load balancing, but in the examples I found
on the internet, they were defined in the workers.list (and yes I tried it
but
Ok,
My mistake. I mixed the examples in the source file the wrong way.
But now it gives me the same error as when I try to configure it without
load balancer:
[Fri Jan 27 08:24:52 2006] [1532:3412] [debug] jk_uri_worker_map.c (475):
Found a wildchar match wlb - /*.jsp
[Fri Jan 27 08:24:52 2006]
