Women in Technology

Hear us Roar

  Integrating Tomcat with Apache Via the mod_jk Module
Subject:   "did not found a worker" Error...
Date:   2002-09-07 10:49:05
From:   chan
Thanks for the great article on integrating apache tomcat using mod_jk on
O'reillyNet. Tomcat works fine independently on port 8080 and apache
correctly serves plain html files in the tomcat examples directory as well
(i.e. Examples menu page). However, I get a 500 Internal Server Error when
accessing any of the example .jsp and servlet files. Mod_jk.log says "did
not found a worker." any help would be greatly appreciated.

I have apache 1.3.26, jakarta-tomcat-4.0.4, jakarta-tomcat-connectors-4.1.9

My workers.properties file:

# Setup for Mac OS X
worker.list=ajp12, ajp13
# Definition for Ajp13 worker

Server.xml file has the following Ajp13 connector listening on port 8009
(didn't change anything here).

<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>

Virtual host block:

<IfModule mod_jk.c>
JkWorkersFile /usr/local/Tomcat/conf/workers.properties
JkLogFile /usr/local/Tomcat/logs/mod_jk.log
JkLogLevel debug

JkMount /*.jsp ajp13
JkMount /servlet/* ajp13

Alias /tomcat/examples /usr/local/Tomcat/webapps/examples

<Directory "/usr/local/Tomcat/webapps/examples">
Options Indexes FollowSymLinks

JkMount /tomcat/examples/servlet/* ajp13
JkMount /tomcat/examples/*.jsp ajp13

<Location "/tomcat/examples/META-INF/">
AllowOverride None
deny from all

Tail of mod_jk.log:

Into jk_uri_worker_map_t::map_uri_to_worker
Attempting to map URI '/tomcat/examples/jsp/dates/date.jsp'
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp
Into wc_get_worker_for_name ajp13
wc_get_worker_for_name, done did not found a worker

Full Threads Oldest First

Showing messages 1 through 6 of 6.

  • "did not found a worker" Error...
    2004-04-21 18:48:10  srw [View]

    I have tried this and it still doesn't work. In looking at the mod_jk.log file when I restart apache, it seems that the only user that it adds is ajp12 on port 8007. Unfortunately, I'm using tomcat 4.1.12, which doesn't support that protocol it needs ajp13 on port 8009). Besides, I have no idea where it is getting that user from. I don't have ajp12 defined anywhere in any configuration file I can find - certainly not in workers.properties.

    Any suggestions would be most appreciated!!!
  • "did not found a worker" Error...
    2003-04-21 17:45:31  anonymous2 [View]

    I had the same problem until I moved all of the Jk commands outside of the virtual host block except for the JkMount statements.

    So put these in the httpd.conf file outside of the virtual host block:

    JkWorkersFile /usr/local/Tomcat/conf/workers.properties
    JkLogFile /usr/local/Tomcat/logs/mod_jk.log
    JkLogLevel debug

    • "did not found a worker" Error...
      2003-07-23 08:10:10  anonymous2 [View]

      Yes! I had this error, and the post below was the answer. move all JK* commands outside the httpd.conf virtualhost and only leave behind the expression to tell apache which pages to send to mod_jk, namely "JkMount /*jsp" and any others
  • "did not found a worker" Error...
    2003-03-02 20:06:31  dberg [View]

    I too have the same error. Did you ever find a fix for the error?

  • "did not found a worker" Error...
    2003-02-05 16:36:56  anonymous2 [View]

    Did anyone solve your "wc_get_worker_for_name, done did not found a worker" problem?

    I've encountered the same problem and have run out of ideas for troubleshooting.

    Any help would be greatly appreciated.
    • "did not found a worker" Error...
      2006-01-27 04:30:56  baegsi [View]

      JkWorkersFile ...
      JkLogFile ...
      JkLogLevel ...

      inton httpd.conf worked for me too!