-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, June
20, 2003 11:23 AM
To: Tomcat Users List
Subject: SPAM: Re: mod_jk quirk?
[Message inserted by SAS Postmaster: ISD is evaluating gateway-level
spam defenses. This message was judged by one of the filters being
Thanks both of you! This answers my question. -Dave
-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 21, 2003 2:03 AM
To: [EMAIL PROTECTED]
Subject: Re: mod_jk quirk?
Larry is correct. The worker is configurable. The Jk docs are a mess
When I auto-generate the mod_jk directives, I'm finding strange behavior: Even if my
workers.properties file contains the name of a worker other than ajp13, the JkMount
commands that get generated always have the worker name as ajp13.
for example, if I put the following in my
Hi -
AFAIK, Tomcat never reads workers.properties, only mod_jk reads
workers.properties.
If you use the auto-generation, your worker will always be named ajp13. If
you need something else, you need to configure things manually. The
ApacheConfig classes are a convenience, not a requirement,
OK, I appreciate your response. -Dave
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED]
Sent: Friday, June 20, 2003 11:23 AM
To: Tomcat Users List
Subject: SPAM: Re: mod_jk quirk?
[Message inserted by SAS Postmaster: ISD is evaluating gateway-level spam defenses
AM
To: Tomcat Users List
Subject: SPAM: Re: mod_jk quirk?
[Message inserted by SAS Postmaster: ISD is evaluating
gateway-level spam defenses. This message was judged by one
of the filters being evaluated to be spam. If this message is
in fact spam, ** there is no action you need to take
List
Subject: SPAM: Re: mod_jk quirk?
[Message inserted by SAS Postmaster: ISD is evaluating
gateway-level spam defenses. This message was judged by one
of the filters being evaluated to be spam. If this message is
in fact spam, ** there is no action you need to take **.
Should our
