On 16.12.2009 15:52, Carlos Ortiz wrote:
Hi all ready fix your comments [same problem ] , sorry about the subject
should read Could not init service for worker=avizpado
Any Ideas ????

No, especially not because you didn't post the new configuration and I don't know what "all ready fix your comments" means in terms of configuration.

Double check you JkOptions as described in my previous mails.

Regards,

Rainer

Rainer Jung escribió:
On 16.12.2009 12:52, Rainer Jung wrote:
===================== Vhost Settings
====================================
#MOD JK
JkOptions +ForwardURIProxy
JkOptions +ForwardURIEscaped

The above two lines are likely the culprit. "+ForwardURIProxy" is the
default and is incompatible with "+ForwardURIEscaped". Since it comes
last, "+ForwardURIEscaped" will win. So far no real problem, but then
you hit a bug in the merging code, which results in having both
"+ForwardURIProxy" (default coming from global server) and
"+ForwardURIEscaped" (vhost) set. This will lead to the observed
problem. Remove the above two lines in case you are not 100% sure, that
you need "+ForwardURIEscaped". If you need it, put it into the global
configuration. Will fix the merge issue for the next release.

... actually it already has been fixed in version 1.2.27, it's issue
44738. So when using the most recent release 1.2.28, the merging
problem should be fixed. Nevertheless it's not a good idea to try
setting both of:

JkOptions +ForwardURIProxy
JkOptions +ForwardURIEscaped

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to