Hi, >>> [EMAIL PROTECTED] 16-10-2007 14:52:45 >>> > 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.
Yup, Apache can find and read the file, it's world-readable. > 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. Nice test. I tried it, but it yields exactly the same. I removed the reference to the workers.properties file and included the JkWorkerProperty statements in httpd.conf. Unfortunately the messages that appear in the log are exactly the same... Looks like the workers.properties file is being read correctly. > By the way: the JkWorkersFile directive should be included in the global > part of the httpd configuration, not inside a virtual server. I noticed :) Apache complained when I did a config check the first time (I added it to the VirtualHost at first). > 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 See below. I switched logging to "trace", restarted Apache and did the request. This is the log. Kind regards, Hans
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
