tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Salazar <>
Subject RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
Date Thu, 16 Jan 2003 20:18:14 GMT
OK, I wasn't clear about the I was thinking that it
was also used by tomcat. I thought that I could configure several
workers by in configuration file that a tomcat would create on
initialization. Workers to me were processes: 2 workers for apj13, more
2 for apj14, .... But, workers are just *tomcat instances*! In that
context, only have meaning to apache! I'm clear now,

To have several tomcat instances in one machine, they must run in
different ports. To achieve that we should create several Connectors
configured in different ports on the server.xml, or should we run
different processes (different JVMs) by running several "catalinas"?
So, what could be wrong when I use the CoyoteConnector? The should be the same as for the Apj13Connector, and it
works with me! 

On Thu, 2003-01-16 at 19:29, Turner, John wrote:
> Sorry, I'm just not clear what you are asking.  Mod_jk uses
> for information on how to reach Tomcat.  That's
> all...that file is not used by CoyoteConnector in any way.  Regarding
> mod_jk2, anything I could tell you would be a guess, as I do not use JK2.
> Unless you have a JkMount directing an image URL like "/*.gif" to Tomcat,
> then Apache will serve that content, not Tomcat.  Tomcat only knows about
> URLs that are in JkMount statements.  If the content is in a WAR file,
> Apache has no way to get to that content.  If you are going to use a JkMount
> statement that sends static and dynamic content requests to Tomcat, there's
> really no reason to use Apache at all, in which case the question is moot.
> Unless you have some sort of legacy requirement or requirement to use
> mod_rewrite or some other Apache modules in addition to mod_jk.
> John

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

View raw message