Hans van Zijst wrote:
>> How does that file look like? Are the paths OK? Does that file really
>> get read in?
>
> The mod_jk.log is posted above. If I need to see the messages you
posted, I assume that somehow the workers.properties is not being read
during startup. This is how mod_jk is loaded in Apache:
>
> LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so
> JkWorkersFile /etc/apache2/workers.properties
>
> This is the config that's included in Apache. The paths are ok.
>
> I found quite a few Tomcat messages in my syslog.
Tomcat errors should be irrelevant at this stage, your mod_jk doesn't
initialize correctly, even before trying to context tomcat.
You could double check, if the Apache user can really read
/etc/apache2/workers.properties.
As a temporary workaround, since your workers.properties is very small,
you could try JkWorkerProperty directives. Each line
a.b.c=d
of workers.properties can also be given directly in an httpd.conf include as
JkWorkerProperty a.b.c=d
If that works, we definitely know, that the problo"em lies in finding the
correct workers.properties. Your situation is definitely strange. No
problems related to your symptoms are known.
By the way: the JkWorkersFile directive should be included in the global
part of the httpd configuration, not inside a virtual server.
Last thing: if you post the jk log again with JkLogLevel trace, I can
check against the normal startup lines and detect the first step during
startup that's missing. Log level trace will log most function calls at
function entry and return.
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
