The workers.properties is identical in format to a version that is
working just fine with Apache 2.
Its starts with the usual..
ps=/
worker.list=jkstatus,gealnx5:12089,...
worker.jkstatus.type=status
worker.gealnx5:12089.type=ajp13
worker.gealnx5:12089.host=...
worker.gealnx5:12089.port=12089
... etc ...
Yes, I recognize that the ':' is noted in the documentation as an
illegal character for the work name- unfortunately all of our jvmRoutes
(hundreds of them in server.xml's on lots of machines) already use this
format host:port. Since jk1 requires that the worker name match the
jvmRoute, we've had to use that when converting our mod_jk2 configs over
using an automated conversion script in perl. However, I did testing
before doing this to confirm that the ':' did not cause an issue in
Apache 2/mod_jk 1.2.10. So if this was the problem with what I'm seeing
in apache 1.3, then there would be some difference in behavior between
the apache 1.3 and 2.
It uses a urimap.properties file instead of JkMounts.
The config directives in httpd.conf look like:
<IfDefine MOD_JK>
JkLogLevel debug
JkShmSize 300
JkShmFile /usr/local/apache/logs/jk1-ssodev.shm
JkWorkersFile /usr/local/apache/conf/workers_sso.properties
JkMountFile /usr/local/apache/conf/uriworkermap_sso.properties
JkLogFile /usr/local/apache/logs/mod_jk-ssodev.log
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkRequestLogFormat "%w %V %T"
<Location /jkstatus/>
JkMount jkstatus
Order deny,allow
Deny from all
Allow from 3.
Allow from 127.
</Location>
</IfDefine>
As you can see from my previous posting, not even jkstatus works, nor do
any workers. Yet, they are configured properly and the jk log shows
that it finds them:
[Mon Apr 18 15:46:11 2005] [7037:0000] [debug]
map_uri_to_worker::jk_uri_worker_map.c (455): Attempting to map URI
'/jkstatus /' from 1 maps
[Mon Apr 18 15:46:11 2005] [7037:0000] [debug]
map_uri_to_worker::jk_uri_worker_map.c (467): Attempting to map context
URI '/ jkstatus/'
[Mon Apr 18 15:46:11 2005] [7037:0000] [debug]
map_uri_to_worker::jk_uri_worker_map.c (492): Found an exact match
jkstatus -> /jkstatus/
[Mon Apr 18 15:46:11 2005] [7037:0000] [debug]
wc_get_worker_for_name::jk_worker.c (94): did not find a worker jkstatus
[Mon Apr 18 15:46:11 2005] [7037:0000] [error] jk_handler::mod_jk.c
(1813): Could not init service for worker=jkstatus
Byron
-----Original Message-----
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 2:03 AM
To: Tomcat Users List
Subject: Re: jk 1.2.10 + apache 1.3 issue
Guernsey, Byron (GE Consumer & Industrial) wrote:
>
> The "NULL factory for ajp13*ajp13" looks odd to me...but that seems
> like an error create 1 worker and I didn't expect it to cause no
> workers to be available. I don't really want to run this with Apache
> 1.3 long term, but I understood it should work...
>
It has nothing to do with Apache version, but rather with your
configuration.
It would be helpful (to you) if you send the workers.properties.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
