RE: ajp12 vs ajp13 mod_jk.conf-auto

2001-02-14 Thread Coetmeur, Alain



 -Message d'origine-
 De: Mel Martinez [mailto:[EMAIL PROTECTED]]
 Date: mardi 13 fvrier 2001 23:33
 : [EMAIL PROTECTED]
 Objet: ajp12 vs ajp13  mod_jk.conf-auto
 
 
 Question:
 
 what determines whether ajp12 or ajp13 will be
 specified for a jkmount statement in the
 auto-generated mod_jk.conf-auto file?
 
 I.E., it always generates statements like:
 
 JkMount /myapp/servlet/* ajp12
 JkMount /myapp/*.jsp ajp12
 
 I've even tried disabling all reference to ajp12 from
 server.xml and workers.properties but that had no
 effect.
 
 Is the only way to force the use of Ajp13 to manually
 edit the mod_jk.conf file?

as told here you can tweak things, but
the most clean is to use
a separate my-mod_jk.conf include file
that you derivate from the generated mod_jk.conf-auto

if you really want all to be automatic
add a conversion script (sed or perl script) 
to generate the my-mod_jk.conf from the .conf-auto

with cocoon and HTTPS I had to tweak 
thos .conf-auto much more and
nothing is better than manual config when things are stable...

changing the ajp12 alias to point to ajp13 is
really anti-documentation...
on unix try something like

#!/bin/sh
launch_tomcat
sleep 5 # wait for tomcat to generate the .conf-auto
sed -e 's/ajp12/ajp13/g' conf/mod_jk.conf-auto conf/my-mod_jk.conf
launch_apache


don't forget to adapt apache conf/httpd.conf to include
the my-mod_jk.conf instead of the conf-auto


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: ajp12 vs ajp13 mod_jk.conf-auto

2001-02-13 Thread Filip Hanik

yes,
the JkMount command looks like this

JkMount context workername

so the autogenerated ajp12 is just the worker name "ajp12"

in the workers.properties file you can change the protocol that the worker
is using.
the property file has the following format

worker.workername.propertyname=value
worker.ajp12.port=8007
worker.ajp12.host=localhost
worker.ajp12.type=ajp13

so just change the last line to use ajp13. now you have to modify server.xml
to start a ajp13 connector on the port 8007 and change the port for ajp12.

the nice thing with the autogenerated file is that your webapps can be
dynamic.
but if you need to do a lot of fancy stuff, you should create your own file
for the mod_jk configuration.

try playing around with it, and if you have a specific problem let me know
and I can help you out.

Filip

~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
- Original Message -
From: "Mel Martinez" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 13, 2001 2:32 PM
Subject: ajp12 vs ajp13  mod_jk.conf-auto


 Question:

 what determines whether ajp12 or ajp13 will be
 specified for a jkmount statement in the
 auto-generated mod_jk.conf-auto file?

 I.E., it always generates statements like:

 JkMount /myapp/servlet/* ajp12
 JkMount /myapp/*.jsp ajp12

 I've even tried disabling all reference to ajp12 from
 server.xml and workers.properties but that had no
 effect.

 Is the only way to force the use of Ajp13 to manually
 edit the mod_jk.conf file?

 Should I even be worrying about this?

 Thanks,

 mel

 __
 Do You Yahoo!?
 Get personalized email addresses from Yahoo! Mail - only $35
 a year!  http://personal.mail.yahoo.com/

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: ajp12 vs ajp13 mod_jk.conf-auto

2001-02-13 Thread Mel Martinez

Thanks, Filip.

I'll try the changes you suggested.

Now, if I could just get someone to tell me why apache
Alias and Rewrites are not working with tomcat...


Mel



--- Filip Hanik [EMAIL PROTECTED] wrote:
 yes,
 the JkMount command looks like this
 
 JkMount context workername
 
 so the autogenerated ajp12 is just the worker name
 "ajp12"
 
 in the workers.properties file you can change the
 protocol that the worker
 is using.
 the property file has the following format
 
 worker.workername.propertyname=value
 worker.ajp12.port=8007
 worker.ajp12.host=localhost
 worker.ajp12.type=ajp13
 
 so just change the last line to use ajp13. now you
 have to modify server.xml
 to start a ajp13 connector on the port 8007 and
 change the port for ajp12.
 
 the nice thing with the autogenerated file is that
 your webapps can be
 dynamic.
 but if you need to do a lot of fancy stuff, you
 should create your own file
 for the mod_jk configuration.
 
 try playing around with it, and if you have a
 specific problem let me know
 and I can help you out.
 
 Filip
 
 ~
 Namaste - I bow to the divine in you
 ~
 Filip Hanik
 Software Architect
 [EMAIL PROTECTED]
 www.filip.net
 - Original Message -
 From: "Mel Martinez" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, February 13, 2001 2:32 PM
 Subject: ajp12 vs ajp13  mod_jk.conf-auto
 
 
  Question:
 
  what determines whether ajp12 or ajp13 will be
  specified for a jkmount statement in the
  auto-generated mod_jk.conf-auto file?
 
  I.E., it always generates statements like:
 
  JkMount /myapp/servlet/* ajp12
  JkMount /myapp/*.jsp ajp12
 
  I've even tried disabling all reference to ajp12
 from
  server.xml and workers.properties but that had no
  effect.
 
  Is the only way to force the use of Ajp13 to
 manually
  edit the mod_jk.conf file?
 
  Should I even be worrying about this?
 
  Thanks,
 
  mel
 
  __
  Do You Yahoo!?
  Get personalized email addresses from Yahoo! Mail
 - only $35
  a year!  http://personal.mail.yahoo.com/
 
 

-
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  For additional commands, email:
 [EMAIL PROTECTED]
 
 
 
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, email:
 [EMAIL PROTECTED]
 


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: ajp12 vs ajp13 mod_jk.conf-auto

2001-02-13 Thread Filip Hanik

 Now, if I could just get someone to tell me why apache
 Alias and Rewrites are not working with tomcat...

tell us what you are trying to do and send us some sample config files and
how your environment is setup. is becomes much easier than to answer the
question above, because alias works very well for me :)

Filip

~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
- Original Message -
From: "Mel Martinez" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 13, 2001 3:11 PM
Subject: Re: ajp12 vs ajp13  mod_jk.conf-auto


 Thanks, Filip.

 I'll try the changes you suggested.

 Now, if I could just get someone to tell me why apache
 Alias and Rewrites are not working with tomcat...


 Mel



 --- Filip Hanik [EMAIL PROTECTED] wrote:
  yes,
  the JkMount command looks like this
 
  JkMount context workername
 
  so the autogenerated ajp12 is just the worker name
  "ajp12"
 
  in the workers.properties file you can change the
  protocol that the worker
  is using.
  the property file has the following format
 
  worker.workername.propertyname=value
  worker.ajp12.port=8007
  worker.ajp12.host=localhost
  worker.ajp12.type=ajp13
 
  so just change the last line to use ajp13. now you
  have to modify server.xml
  to start a ajp13 connector on the port 8007 and
  change the port for ajp12.
 
  the nice thing with the autogenerated file is that
  your webapps can be
  dynamic.
  but if you need to do a lot of fancy stuff, you
  should create your own file
  for the mod_jk configuration.
 
  try playing around with it, and if you have a
  specific problem let me know
  and I can help you out.
 
  Filip
 
  ~
  Namaste - I bow to the divine in you
  ~
  Filip Hanik
  Software Architect
  [EMAIL PROTECTED]
  www.filip.net
  - Original Message -
  From: "Mel Martinez" [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Tuesday, February 13, 2001 2:32 PM
  Subject: ajp12 vs ajp13  mod_jk.conf-auto
 
 
   Question:
  
   what determines whether ajp12 or ajp13 will be
   specified for a jkmount statement in the
   auto-generated mod_jk.conf-auto file?
  
   I.E., it always generates statements like:
  
   JkMount /myapp/servlet/* ajp12
   JkMount /myapp/*.jsp ajp12
  
   I've even tried disabling all reference to ajp12
  from
   server.xml and workers.properties but that had no
   effect.
  
   Is the only way to force the use of Ajp13 to
  manually
   edit the mod_jk.conf file?
  
   Should I even be worrying about this?
  
   Thanks,
  
   mel
  
   __
   Do You Yahoo!?
   Get personalized email addresses from Yahoo! Mail
  - only $35
   a year!  http://personal.mail.yahoo.com/
  
  
 
 -
   To unsubscribe, e-mail:
  [EMAIL PROTECTED]
   For additional commands, email:
  [EMAIL PROTECTED]
  
  
 
 
 
 -
  To unsubscribe, e-mail:
  [EMAIL PROTECTED]
  For additional commands, email:
  [EMAIL PROTECTED]
 


 __
 Do You Yahoo!?
 Get personalized email addresses from Yahoo! Mail - only $35
 a year!  http://personal.mail.yahoo.com/

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]