Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[jean-frederic clere]

Mark Thomas wrote:

[EMAIL PROTECTED] wrote:

   For additional help, the best resource is the Tomcat Users 
Discussion list. You should start by searching

  -http://mikal.org/interests/java/tomcat/index.html";>
  +href="http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]"> 


   the mail list archive
   before you post questions to the list. If you are unable to 
locate the answer to your question in the archive, 



Eyebrowse has been turned off. The new URL should be:
http://mail-archives.apache.org/mod_mbox/jakarta-tomcat-user/


Fixed thanks.




-
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]

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[jfclere]

jfclere 2005/07/05 00:12:51

  Modified:jk/xdocs faq.xml
  Log:
  Eyebrowse has been turned off. Thanks Mark Thomas (markt).
  
  Revision  ChangesPath
  1.14  +2 -2  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- faq.xml   4 Jul 2005 07:41:07 -   1.13
  +++ faq.xml   5 Jul 2005 07:12:51 -   1.14
  @@ -39,7 +39,7 @@
   Jakarta Tomcat Connectors Project
   For additional help, the best resource is the Tomcat Users Discussion list.  
   You should start by searching
  -http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]">
  +http://mail-archives.apache.org/mod_mbox/jakarta-tomcat-user/";>
   the mail list archive
   before you post questions to the list.  
   If you are unable to locate the answer to your question in the archive, 
  
  
  

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

Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[Mark Thomas]

[EMAIL PROTECTED] wrote:
   For additional help, the best resource is the Tomcat Users Discussion list.  
   You should start by searching

  -http://mikal.org/interests/java/tomcat/index.html";>
  +http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]">
   the mail list archive
   before you post questions to the list.  
   If you are unable to locate the answer to your question in the archive, 


Eyebrowse has been turned off. The new URL should be:
http://mail-archives.apache.org/mod_mbox/jakarta-tomcat-user/


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

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[jfclere]

jfclere 2005/07/04 00:41:07

  Modified:jk/xdocs faq.xml
  Log:
  Arrange links and a typo. PR 13911.
  
  Revision  ChangesPath
  1.13  +5 -5  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- faq.xml   30 Nov 2004 07:35:37 -  1.12
  +++ faq.xml   4 Jul 2005 07:41:07 -   1.13
  @@ -39,7 +39,7 @@
   Jakarta Tomcat Connectors Project
   For additional help, the best resource is the Tomcat Users Discussion list.  
   You should start by searching
  -http://mikal.org/interests/java/tomcat/index.html";>
  +http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]">
   the mail list archive
   before you post questions to the list.  
   If you are unable to locate the answer to your question in the archive, 
  @@ -69,7 +69,7 @@
   
   
   JK is a project covering web-servers to Tomcat connectors,
  -whereas mod_jk is the Apache module 
developped in JK.
  +whereas mod_jk is the Apache module 
developed in JK.
   
   
   
  @@ -128,7 +128,7 @@
   
   
   
  -Ajp13 is a newer protocol, it's faster, and 
it works better with SSL. 
  +Ajp13 is a newer protocol, it's faster, 
and it works better with SSL. 
   You almost certainly want to use it now that ajp12 is 
deprecated.
   

  @@ -180,7 +180,7 @@
   
   
   
  -Many versions of Apache use of modified API, known at Extended API, 
developped for use with the
  +Many versions of Apache use of modified API, known at Extended API, 
developed for use with the
   http://www.modssl.org";>mod_ssl module.
   
   
  
  
  

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

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[glenn]

glenn   2003/11/01 11:16:45

  Modified:jk/xdocs faq.xml
  Log:
  Fix an href
  
  Revision  ChangesPath
  1.9   +2 -2  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- faq.xml   31 Oct 2003 13:50:04 -  1.8
  +++ faq.xml   1 Nov 2003 19:16:45 -   1.9
  @@ -15,7 +15,7 @@
   The primary mechanism for support is through the JK 
   documentation included in the doc directory.
   Documentation is also available on the Apache Jakarta web site devoted to the
  -http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html";
  +http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html";>
   Jakarta Tomcat Connectors Project
   For additional help, the best resource is the Tomcat Users Discussion list.  
   You should start by searching
  
  
  

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

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[hgomez]

hgomez  2002/11/19 07:21:09

  Modified:jk/xdocs faq.xml
  Log:
  Update FAQ
  
  Revision  ChangesPath
  1.7   +9 -1  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- faq.xml   7 Nov 2002 11:44:09 -   1.6
  +++ faq.xml   19 Nov 2002 15:21:09 -  1.7
  @@ -289,6 +289,14 @@
   
   
   
  +
  +
  +In JK2 before v2.0.2, you should add #define BSD_COMP in top
  +of jk/native2/common/jk_channel_socket.c to have Solaris build succeed.
  +
  +
  +
  +
   
   
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[hgomez]

hgomez  2002/11/07 03:44:09

  Modified:jk/xdocs faq.xml
  Log:
  Some clarifications about build via configure
  
  Revision  ChangesPath
  1.6   +14 -1 jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq.xml   7 Nov 2002 09:16:35 -   1.5
  +++ faq.xml   7 Nov 2002 11:44:09 -   1.6
  @@ -276,6 +276,19 @@
   
   
   
  +
  +
  +configure assume you have some GNU tools allready installed and configured for your 
system, and ad minima libtool.
  +
  +
  +Also some systems may have mixed cc and gcc setup which may make you puzzled when 
trying to link an Apache built with native
  +c compiler with a jk/jk2 build with gcc.
  +
  +
  +In fine some native make didn't works as expect so you should use a GNU make 
gmake.
  +
  +
  +
   
   
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[hgomez]

hgomez  2002/11/07 01:16:35

  Modified:jk/xdocs faq.xml
  Log:
  Update faq
  
  Revision  ChangesPath
  1.5   +6 -1  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- faq.xml   24 Sep 2002 10:23:51 -  1.4
  +++ faq.xml   7 Nov 2002 09:16:35 -   1.5
  @@ -71,6 +71,11 @@
   
   
   
  +
  +
  +For the impatients
  +
  +
   
   Apache and JK
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[Henri Gomez]

Bojan Smojver wrote:
> I think this also applies to 1.3. It's just that MMN in it hasn't been
> changed for a while.
> 

Sure API are stalibilized for sometimes now on 1.3.x



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[Bojan Smojver]

I think this also applies to 1.3. It's just that MMN in it hasn't been
changed for a while.

Bojan

On Tue, 2002-09-24 at 20:23, [EMAIL PROTECTED] wrote:
> hgomez  2002/09/24 03:23:51
> 
>   Modified:jk/xdocs faq.xml
>   Log:
>   Add information about MMNB (Magic Module Number bump) of Apache 2.0
>   
>   Revision  ChangesPath
>   1.4   +2 -2  jakarta-tomcat-connectors/jk/xdocs/faq.xml
>   
>   Index: faq.xml
>   ===
>   RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
>   retrieving revision 1.3
>   retrieving revision 1.4
>   diff -u -r1.3 -r1.4
>   --- faq.xml 20 Sep 2002 21:35:31 -  1.3
>   +++ faq.xml 24 Sep 2002 10:23:51 -  1.4
>   @@ -220,7 +220,7 @@
>
>
>Since Apache 2.0 API still change often, the Apache 2.0 teams decide to put in 
>headers of compiled modules the 
>   -Apache 2.0 version used to compile the module. 
>   +Apache 2.0 version used to compile the module. This check is called Magic Module 
>Number bump.
>
>
>At start time Apache 2.0 check that version in modules headers and stop if it 
>detect that a module was compiled 
>   
>   
>   
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[hgomez]

hgomez  2002/09/24 03:23:51

  Modified:jk/xdocs faq.xml
  Log:
  Add information about MMNB (Magic Module Number bump) of Apache 2.0
  
  Revision  ChangesPath
  1.4   +2 -2  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/faq.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- faq.xml   20 Sep 2002 21:35:31 -  1.3
  +++ faq.xml   24 Sep 2002 10:23:51 -  1.4
  @@ -220,7 +220,7 @@
   
   
   Since Apache 2.0 API still change often, the Apache 2.0 teams decide to put in 
headers of compiled modules the 
  -Apache 2.0 version used to compile the module. 
  +Apache 2.0 version used to compile the module. This check is called Magic Module 
Number bump.
   
   
   At start time Apache 2.0 check that version in modules headers and stop if it 
detect that a module was compiled 
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml index.xml

[hgomez]

hgomez  2002/09/10 01:02:50

  Modified:jk/xdocs/jk workershowto.xml iishowto.xml aphowto.xml
neshowto.xml domhowto.xml
   jk/xdocs/common AJPv14-proposal.xml AJPv13.xml
   jk/xdocs faq.xml index.xml
  Log:
  Fixes typos and styles
  
  Revision  ChangesPath
  1.3   +12 -10jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml
  
  Index: workershowto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- workershowto.xml  9 Sep 2002 09:56:35 -   1.2
  +++ workershowto.xml  10 Sep 2002 08:02:49 -  1.3
  @@ -73,7 +73,7 @@
   
   Each named worker should also have a few entries to provide additional information 
on his behalf.
   This information includes the worker's type and other related worker information. 
  -Currently the following worker types that exists are (jk 1.2.0):
  +Currently the following worker types that exists are (JK 1.2.0):
   
   
   
  @@ -203,13 +203,13 @@
   
   
   
  -cachesize property is usefull when you're using jk in multithreaded 
  +cachesize property is usefull when you're using JK in multithreaded 
   web servers such as Apache 2.0, IIS and Netscape. They will benefit the most by 
   setting this value to a higher level (such as the estimated average concurrent 
users for Tomcat).
   
   
   
  -cache_timeout property should be used with cachesize to specify how 
to time jk should keep
  +cache_timeout property should be used with cachesize to specify how 
to time JK should keep
   an open socket in cache before closing it. This property should be used to reduce 
the number of threads 
   on the Tomcat WebServer.
   
  @@ -244,9 +244,11 @@
   
   
   
  -socket_timeout property told webserver to cut an ajp13 connection after some 
time of use.
  -It's a good way to ensure that there won't be any unused threads living on Tomcat 
side, with the
  -extra cost of reopening sockets next time a request be forwarded.
  +socket_timeout property told webserver to cut an ajp13 connection after some 
time of 
  +inactivity. When choosing an endpoint for a request and the assigned socket is 
open, it will be
  +closed if it was not used for the configured time.
  +It's a good way to ensure that there won't too old threads living on Tomcat side, 
  +with the extra cost you need to reopen the socket next time a request be forwarded.
   This property is very similar to cache_timeout but works also in non-cache 
mode.
   
   
  @@ -323,7 +325,7 @@
   Note: Since the JVM is multithreaded; the jni worker should be used only within 
multithreaded servers 
   such as AOLServer, IIS, Netscape and Apache 2.0. 
   You should also make sure that the threading scheme used by the web servers match 
the one 
  -used to build the jk web server plugin.
  +used to build the JK web server plugin.
   
   
   
  @@ -344,7 +346,7 @@
   
   
   The class_path property can be given in multiple lines. 
  -In this case the jk environment will concatenate all the classpath entries together 
  +In this case the JK environment will concatenate all the classpath entries together 
   by putting path delimiter (":"/";") between the entries.
   
   
  @@ -361,7 +363,7 @@
   
   
   The cmd_line property can be given in multiple lines. 
  -In this case the jk environment will concatenate all the cmd_line entries together 
by putting spaces 
  +In this case the JK environment will concatenate all the cmd_line entries together 
by putting spaces 
   between the entries.
   
   
  @@ -458,7 +460,7 @@
   
   
   Since coping with worker.properties on your own is not an easy thing to do, 
  -a sample worker.properties file is bundled along jk. 
  +a sample worker.properties file is bundled along JK. 
   
   
   
  
  
  
  1.3   +1 -1  jakarta-tomcat-connectors/jk/xdocs/jk/iishowto.xml
  
  Index: iishowto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/iishowto.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- iishowto.xml  9 Sep 2002 09:57:10 -   1.2
  +++ iishowto.xml  10 Sep 2002 08:02:49 -  1.3
  @@ -13,7 +13,7 @@
   
   
   Normally IIS can not execute Servlets and Java Server Pages (JSPs), 
  -configuring IIS to use the mod_jk redirector plugin will let IIS send servlet and 
  +configuring IIS to use the JK ISAPI redirector plugin will let IIS send servlet and 
   JSP requests to Tomcat (and this way, serve them to clients).
   
   
  
  
  
  1.5   +4 -4  jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml
  
  Index: aphowto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml,v
  retrieving revision 1.4
  re

cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml

[hgomez]

hgomez  2002/09/02 03:50:23

  Added:   jk/xdocs faq.xml
  Log:
  The long awaited FAQ is now on it's own file
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-connectors/jk/xdocs/faq.xml
  
  Index: faq.xml
  ===
  
  
  
  FAQ
  Henri Gomez
  
  
  
  
  General Informations and FAQ about mod_jk
  
  
  
  The primary mechanism for support is through the mod_jk 
  documentation included in the doc directory.
  Documentation is also available on the Apache Jakarta web site devoted to the
  http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/doc/index.html";>
  Jakarta Tomcat Connectors Project
  For additional help, the best resource is the Tomcat Users Discussion list.  
  You should start by searching
  http://mikal.org/interests/java/tomcat/index.html";>
  the mail list archive
  before you post questions to the list.  
  If you are unable to locate the answer to your question in the archive, 
  you can post questions about mod_jk to the user list for assistance.  
  Make sure that you include the version of your Webserver, 
  that you are using as well as the platform you are running on
  and go 
  http://jakarta.apache.org/site/mail.html";>
  here
  to determine how to subscribe to tomcat mailing list.
  
  
  
  
  
  Now that mod_jk moved to the jakarta-tomcat-connectors repository, 
  the source and binaries for mod_jk are present 
  in the http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/";>
  jakarta-tomcat-connectors directory
  
  
  
  
  
  For mod_jk 1.2.x the 
  mod_jk-config howto document has considerably more in-depth information.
  For mod_jk 2.0.x the 
  config tomcat and config webserver
  documents have considerably more in-depth information.
  It's worth a look. 
  You could also try searching the mailing list archives for "mod_jk" or look at the 
source.
  
  
  
  
  
  Ajp13 is a newer protocol, it's faster, and it 
works better with SSL. You almost certainly want to use it. 
  There is more information in the workers.properties howto document, ajp12 is now 
deprecated. 
  Also ajp13 is supported by all Apache Tomcat  including 3.2.x , 3.3.x, 4.0.x, 4.1.x 
and the new tomcat 5. 
  Others Servlet engine like jetty have support for Ajp13.
  
  
  
  
  
  Ajp13 use persistant connections where the traffic could be null if there is no 
request to be sent to Tomcat. 
  Firewall used to drop inactive connections and will make your WebServer and Tomcat 
think the connection is valid. 
  Since mod_jk 1.2.0 a socket_keepalive property as been added to ajp13 settings, and 
you should take a look at 
  it in workers.properties howto
  
  
  
  
  
  Under heavy load, Apache WebServer create many childs to handle the load, which will 
in turn create many connections 
  to Tomcat to forward the requests they should handle. 
  Apache WebServer will normally kill the childs/threads when the load decrease. But 
if the load is still there and 
  even if only Apache handle the requests, ie static contents, the childs are kept and 
with them the ajp13 connections, 
  even if they are no more used. 
  Since mod_jk 1.2.0 cache_timeout and socket_timeout properties as been added to 
close connections after some time, 
  for more informations refer to workers.properties howto
  
  
  
  
  
  
  
  Informations and FAQ about mod_jk and Apache Web Servers. 
  
  
  
  The Ajp13 protocol keeps an open socket between Tomcat and Apache. Release of mod_jk 
present in J-T-C handle the network failure. 
  But with previous release of mod_jk, you may have to restart Apache as well.
  
  
  
  
  
  Many versions of Apache use of modified API, known at Extended API. For example, 
Apache using mod_ssl or 
  Apache present in certains recent Linux distributions. So if you got such 'Extended 
Apache', 
  you need to use mod_jk.so-eapi, or use mod_jk.so-noeapi for standard Apache. 
  It's wise to avoid using EAPI modules on STD API Apache or to use standard API 
modules on EAPI Apache. 
  Allways be sure to have the mod_jk.so for your version of Apache
  
  
  
  
  
  It's related to Apache EAPI, the message 'mod_jk.so is garbled - perhaps this is not 
an Apache module DSO ?' 
  just told you are trying to install a mod_jk.so DSO module that was compiled on an 
Apache using EAPI, 
  like apache-mod_ssl or apache from Redhat distro 6.2/7.0 but your system use the 
standard apache with normal API.
  
  
  
  
  
  Also related to EAPI, the message '[warn] Loaded DSO /usr/lib/apache/mod_jk.so uses 
plain Apache 1.3 API, 
  this module might crash under EAPI! (please recompile it with -DEAPI)', the 
mod_jk.so was compiled under normal 
  Apache with standard API and you try to install the module on an Apache using EAPI.
  
  
  
  
  
  APXS is a Perl script that is crea