tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pushkar Tiwari <>
Subject mod_jk not creating worker other than ajp13
Date Thu, 09 Sep 2010 12:14:00 GMT
Hi All,

I am trying to connect Tomcat 6.0.16 with Apache 2.2.16 through mod_jk 1.2.30 on Win XP service
pack 3 32 bit platform.

I have followed following steps:

 *   Placing into apache/modules.
 *   Creating mod_jk.conf & files in apache/conf
 *   Modifying https.conf and including mod_jk.conf (only add -> Include conf/mod_jk.conf)
 *   Content of mod_jk.conf is as follows:

# mod_jk.conf start
LoadModule jk_module modules/

JkWorkersFile conf/
JkLogFile logs/mod_jk.log
            JkLogLevel debug
            JkLogStampFormat  "[%a %b %d %H:%M:%S %Y]"
            JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
            JkRequestLogFormat "%w %V %T"

JkMount /TestLB1 jvm1
JkMount /TestLB1/* jvm1

JkShmFile logs/jk.shm
# mod_jk.conf end

 *   Content of is as follows:


 *   In tomcat's server.xml I have a ajp connector

<Connector port="8009" enableLookups="false" protocol="AJP/1.3" redirectPort="8443"/>

Everything starts well except mod_jk, logs are as follow:

[debug] jk_worker.c (242): creating worker ajp13
[debug] jk_worker.c (146): about to create instance ajp13 of ajp13
[debug] jk_worker.c (159): about to validate and init ajp13
[debug] jk_ajp_common.c (2605): worker ajp13 contact is 'localhost:8009'
[debug] jk_ajp_common.c (2800): setting endpoint options:
[debug] jk_ajp_common.c (2803): keepalive:              0
[debug] jk_ajp_common.c (2807): socket timeout:         0
[debug] jk_ajp_common.c (2811): socket connect timeout: 0
[debug] jk_ajp_common.c (2815): buffer size:            0
[debug] jk_ajp_common.c (2819): pool timeout:           0
[debug] jk_ajp_common.c (2823): ping timeout:           10000
[debug] jk_ajp_common.c (2827): connect timeout:        0
[debug] jk_ajp_common.c (2831): reply timeout:          0
[debug] jk_ajp_common.c (2835): prepost timeout:        0
[debug] jk_ajp_common.c (2839): recovery options:       0
[debug] jk_ajp_common.c (2843): retries:                2
[debug] jk_ajp_common.c (2847): max packet size:        8192
[debug] jk_ajp_common.c (2851): retry interval:         100
[info] mod_jk.c (3189): mod_jk/1.2.30 initialized
[debug] jk_worker.c (116): did not find a worker jvm1
[error] jk_uri_worker_map.c (506): Could not find worker with name 'jvm1' in uri map post
[debug] jk_worker.c (116): did not find a worker jvm1
[error] jk_uri_worker_map.c (506): Could not find worker with name 'jvm1' in uri map post

And If I use worker name ajp13 which is default one it always works,I don't understand why
its always going to create worker name ajp13 for localhost & port 8009 which is default
one despite of my custom worker name.
Any suggestions?

Thanks ,


The contents of this e-mail and any attachment(s) are confidential and intended for the named
recipient(s) only. 
It shall not attach any liability on the originator or HCL or its affiliates. Any views or
opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of
HCL or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and
/ or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited.
If you have 
received this email in error please delete it and notify the sender immediately. Before opening
any mail and 
attachments please check them for viruses and defect.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message