|
Home > Archive > Apache Server configuration support > August 2005 > Problems with mod_jk
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problems with mod_jk
|
|
| slilichenko@yahoo.com 2005-08-30, 6:02 pm |
| I am seeing a very odd behaviour of mod_jk module. Apparently it
doesn't intialize workers from workers.properties, or initializes them
from a different location, or just uses some defaults.
Here's my workers.properties:
worker.list=tomcat1
worker.tomcat1.port=8010
worker.tomcat1.host=<my tomcat server ip>
worker.tomcat1.type=ajp13
worker.tomcat1.lbfactor=1
and this is the section of httpd.conf related to mod_jk:
#JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkMount /nlighten/*.html tomcat1
JkShmFile logs/jk.shm
JkWorkersFile /etc/httpd/conf/workers.properties
JkLogFile logs/mod_jk.log
JkLogLevel trace
Here's the output of the mod_jk.log:
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace]
map_uri_to_worker::jk_uri_worker_map.c (422): enter
[Tue Aug 30 08:49:54 2005] [28402:5824] [debug]
map_uri_to_worker::jk_uri_worker_map.c (449): Attempting to map URI
'/nlighten/login.html' from 1 maps
[Tue Aug 30 08:49:54 2005] [28402:5824] [debug]
map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context
URI '/nlighten/*.html'
[Tue Aug 30 08:49:54 2005] [28402:5824] [debug]
map_uri_to_worker::jk_uri_worker_map.c (475): Found a wildchar match
tomcat1 -> /nlighten/*.html
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace]
map_uri_to_worker::jk_uri_worker_map.c (478): exit
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace] jk_handler::mod_jk.c
(1771): enter
[Tue Aug 30 08:49:54 2005] [28402:5824] [debug] jk_handler::mod_jk.c
(1825): Into handler jakarta-servlet worker=tomcat1 r->proxyreq=0
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace]
wc_get_worker_for_name::jk_worker.c (101): enter
[Tue Aug 30 08:49:54 2005] [28402:5824] [debug]
wc_get_worker_for_name::jk_worker.c (111): did not find a worker
tomcat1
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace]
wc_get_worker_for_name::jk_worker.c (113): exit
[Tue Aug 30 08:49:54 2005] [28402:5824] [info] jk_handler::mod_jk.c
(1979): Could not find a worker for worker name=tomcat1
[Tue Aug 30 08:49:54 2005] [28402:5824] [trace] jk_handler::mod_jk.c
(1982): exit
No errors on initialization of the server or anything like that.
The only way I see any attempts of mod_jk to actually connect if I
JkMount something to a particular name - ajp13. But in that case it
doesn't pick up the parameters from workers.properties (I modified the
worker name to ajp13, of course); it just keeps going to 127.0.0.1 port
8009. workers.properties have -rw-r--r-- permissions.
I am running RH ES 4.
What I did to resolve this:
- rebuild mod_jk from the latest source code (1.2.14.1); based on the
line numbers it executes this code.
- tried to rename workers.properties to see if it picks up a different
one - apache complains.
Is it possible that mod_jk caches workers info somewhere and somehow
doesn't refresh it on the restart (btw, I used both apachectl
stop/start and restart).
I would really appreciate any help with this problem.
Thanks,
Sergei
| |
| slilichenko@yahoo.com 2005-08-30, 6:02 pm |
| Some additional info. I also see error in error_log:
No worker file and no worker options in httpd.conf \nuse JkWorkerFile
to set workers\n. I tried to change the path specified by
JkWorkdersFile from absolute to relative in httpd.conf, but to no
avail.
| |
| IchBin 2005-08-31, 2:53 am |
| slilichenko@yahoo.com wrote:
> Some additional info. I also see error in error_log:
> No worker file and no worker options in httpd.conf \nuse JkWorkerFile
> to set workers\n. I tried to change the path specified by
> JkWorkdersFile from absolute to relative in httpd.conf, but to no
> avail.
>
I did not see the following in your workers_properties file
# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=/usr/local/tomcat
#
# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
#
workers.java_home=/usr/local/java
#
# You should configure your environment slash... ps=\ on NT and / on UNIX
# and maybe something different elsewhere.
#
ps=/
--
Thanks in Advance...
IchBin, Pocono Lake, Pa, USA http://weconsultants.servebeer.com
________________________________________
__________________________________
'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)
| |
| slilichenko@yahoo.com 2005-08-31, 8:57 pm |
| My understanding is that those properties are usually used for
inprocess worker, when, by definition, Tomcat is installed on a local
machine and mod_jk would need to know how to start Java. In my case
Tomcat is on a different server.
IchBin wrote:
> slilichenko@yahoo.com wrote:
> I did not see the following in your workers_properties file
>
> # workers.tomcat_home should point to the location where you
> # installed tomcat. This is where you have your conf, webapps and lib
> # directories.
> #
> workers.tomcat_home=/usr/local/tomcat
> #
> # workers.java_home should point to your Java installation. Normally
> # you should have a bin and lib directories beneath it.
> #
> workers.java_home=/usr/local/java
> #
> # You should configure your environment slash... ps=\ on NT and / on UNIX
> # and maybe something different elsewhere.
> #
> ps=/
>
> --
>
>
> Thanks in Advance...
> IchBin, Pocono Lake, Pa, USA http://weconsultants.servebeer.com
> ________________________________________
__________________________________
>
> 'If there is one, Knowledge is the "Fountain of Youth"'
> -William E. Taylor, Regular Guy (1952-)
|
|
|
|
|