Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change 
notification.

The following page has been changed by markt:
http://wiki.apache.org/tomcat/FAQ/Connectors

The comment on the change is:
Add anchors - ran out of time for list of questions on this page.

------------------------------------------------------------------------------
  
  '''Please note, jk2 is no longer supported. Please use mod_jk instead.'''
  == Questions ==
+ 
- '''What is JK (or AJP)?'''
+ [[Anchor(Q1)]]'''What is JK (or AJP)?'''
  
  AJP is a wire protocol. It an optimized version of the HTTP protocol to allow 
a standalone web server such as Apache talk to Tomcat. Historically, Apache has 
always been much faster than Tomcat at serving static content. The idea is to 
let Apache serve the static content when possible, then proxy the request back 
to Tomcat for Tomcat related content. 
  
- '''Which connector: mod_jserv, JK, JK2, mod_webapp or mod_proxy?'''
+ [[Anchor(Q2)]]'''Which connector: mod_jserv, JK, JK2, mod_webapp or 
mod_proxy?'''
  
   * Stay away from mod_webapp, aka warp. It is deprecated and unsupported due 
to lack of developer interest and there are better options such as jk and jk2. 
It WILL NOT run on windows.
   * mod_jserv is unsupported and will not be supported in Tomcat 5. mod_jserv 
was the original connector which supported the ajp protocol.
@@ -20, +21 @@

   * mod_proxy. A cheap way to proxy without the hassles of configuring JK. 
This solution lacks sticky session load balancing. If you don't need some of 
the features of jk - this is a very simple alternative.
   * mod_proxy_ajp. With apache 2.2, mod_proxy was rewritten to support load 
balancing as well as a new transport called mod_proxy_ajp. This module is 
distributed with the Apache http server, not the Tomcat server.
  
- '''Why should I integrate Apache with Tomcat? (or not)'''
+ [[Anchor(Q3)]]'''Why should I integrate Apache with Tomcat? (or not)'''
  
  There are many reasons to integrate Tomcat with Apache. And there are reasons 
why it should not be done too. Needless to say, everyone will disagree with the 
opinions here. With the performance of Tomcat 5 and 6, performance reasons 
become harder to justify. So here are the issues to discuss in integrating vs 
not.
  
@@ -32, +33 @@

   * Speed. Apache is faster at serving static content than Tomcat. But unless 
you have a high traffic site, this point is useless. But in some scenarios, 
tomcat can be faster than apache. So benchmark YOUR site.
   * Socket handling/system stability. Apache has better socket handling with 
respect to error conditions than Tomcat. The main reason is Tomcat must perform 
all its socket handling via the JVM which needs to be cross platform. The 
problem is socket optimization is a platform specific ordeal. Most of the time 
the java code is fine, but when you are also bombarded with dropped 
connections, invalid packets, invalid requests from invalid IP's, Apache does a 
better job at dropping these error conditions than JVM based program. (YMMV)
  
- '''At boot, is order of start up (Apache vs Tomcat) important?'''
+ [[Anchor(Q4)]]'''At boot, is order of start up (Apache vs Tomcat) 
important?'''
  
  No. This way - either apache or tomcat can be restarted at any time 
independent of one another.
  
- '''Is there any way to control the content of automatically generated 
mod_jk.conf-auto? I need my own specific commands added to it.'''
+ [[Anchor(Q5)]]'''Is there any way to control the content of automatically 
generated mod_jk.conf-auto? I need my own specific commands added to it.'''
  
  There really is no need to. Just copy the automatically generated 
mod_jk.conf-auto and edit it manually to your preference. None of production 
tomcat installations really use mod_jk.conf-auto as it is. 
  
- '''How do I bind to a specific ip address?'''
+ [[Anchor(Q6)]]'''How do I bind to a specific ip address?'''
  
  Each Connector element allows an address property. For example:
  
@@ -53, +54 @@

  
  For a more complete description of the Connector config, see the 
[http://tomcat.apache.org/tomcat-5.0-doc/config/http.html HTTP Connector docs] 
or the see the [http://tomcat.apache.org/tomcat-5.0-doc/config/http.html AJP 
Connector docs].
  
- '''Where can I download a binary distribution of my connector?'''
+ [[Anchor(Q7)]]'''Where can I download a binary distribution of my 
connector?'''
  
  You can't: you need to download the source and compile it for your platform. 
The source distributions are available from the 
[http://tomcat.apache.org/download-connectors.cgi standard location]. Note that 
JPackage.org has RPM distributions for the connectors as well as tomcat itself: 
[http://www.jpackage.org/ JPackage.org]
  
- '''I'm having strange UTF-8 issues with my request parameters.'''
+ [[Anchor(Q8)]]'''I'm having strange UTF-8 issues with my request 
parameters.'''
  
- Since tomcat 5 - does your connector have Connector declaration have 
URIEncoding="UTF-8". For example:
+ Does your connector have Connector declaration have URIEncoding="UTF-8". For 
example:
  
  {{{<Connector port="80"
             maxThreads="50" minSpareThreads="5" maxSpareThreads="15"

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

Reply via email to