RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
Hello - There's no need for jk2.properties with mod_jk. The connector used on the Tomcat side doesn't affect the configuration needed for the Apache module. If you are using mod_jk and not mod_jk2, the only configuration file you need is workers.properties, and that is regardless of using Ajp13Connector or CoyoteConnector on the Tomcat side. CoyoteConnector can handle HTTP, HTTPS, JK, and JK2. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 11:50 AM To: Tomcat Users List Subject: configure CoyoteConnector with mod_jk in tomcat 4.1.x Greetings, I would like to use the CoyoteConnector rather than the Ajp13Connector since I'm using tomcat 4.1(.17) and the listener org.apache.catalina.mbeans.GlobalResourcesLifecycleListener (to have a global database resource) is incompatible with Ajp13Connector (plus the Ajp13Connector will be deprecated facing the CoyoteConnector). But I don't know how to configure the jk2.properties of the CoyoteConnector for tomcat. I have in my apache server pointing to a older worker.properties (simple configuration) that should work with the jk2.properties - I believe that for both of them are required (one for apache and one for tomcat). How should I define the workers list in jk2.properties for they match with the workers.properties of apache? For now I didn't touch in jk2.properties (is all commented). And I have defined a worker called ajp13 (type ajp13) in the workers.properties for apache. My configuration is: -apache2.0.43 + mod_jk -tomcat 4.1.17 -linux redhat 8.0 (2.4.19) thanks, Pedro Salazar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
I can't explain those log messages. I do know that mod_jk uses a single file called workers.properties. I believe, if you use the JkWorkersFile command in httpd.conf, that you can tell mod_jk to use any file you like, like my.properties. So, if you want to use jk2.properties, you probably can. I only use mod_jk, and I can assure you I have no files named jk2.properties. mod_jk2 is a completely different module. It takes different configuration commands, it uses two files instead of one (or can use a single file if you use JkUriSet in httpd.conf). So, the confusion can be clarified by you telling us which module you are using: JK (mod_jk), or JK2 (mod_jk2). Then we can help you figure out your configuration questions, if any. Otherwise we are just going in circles. Regarding your question about the images: where are the images located relative to Apache and Tomcat? Does Tomcat have access to that directory? Does Apache have access to that directory? More information is needed. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:29 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x Greetings, John, if what you said is right why is that happens: 1)when my tomcat starts, it logs a message saying the configuration is the jk.properties: 25984 [main] INFO http11.Http11Protocol - Starting Coyote HTTP/1.1 on port 8080 26167 [main] INFO common.ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 26278 [main] INFO server.JkMain - Jk running ID=0 time=3/294 config=/opt/tomcat/conf/jk2.properties is it also using the workers.properties? (is this the name to use?) 2)and not touching in any apache configuration (pointing to tomcat's workers.properties), the Apj13Connector works just fine, but the CoyoteConnector doesn't log any message in log file! Could you figure why? thanks Pedro Salazar. PS. With my Apj13Connector (the only one I could put it to work yet), accessing the http://localhost/index.jsp (I have a mapping JkMount /*.jsp ajp13), the images don't appear in the default web page of tomcat. Why? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
1- About the Apache, I have no doubts that the mod_jk uses the file defined in JkWorkersFile directive. But, is that clear that Tomcat (4.1.x), I mean the CoyoteConnector, uses only and just only the workers.properties inside $TOMCAT_HOME/conf/? Or could it be in another place? I heard something about workers2.properties, another about conf/jk/workers.properties, I don't know if they were specific for apache or if the location can be defined. I would like to clarify this issue, I mean, the correct file name and location of the configuration of the workers to CoyoteConnector that should be the same for Apj13Connector. 2- About the images, they are located inside WAR files in webapps of tomcat. I tried to use JkAutoAlias /opt/tomcat/webapps but apparently it isn't a known directive of mod_jk (probably only to mod_jk2). So, I thought that by default any request of a image inside a JkMount context should be handled by Apache in transparent way. It appears that I should have a two web applications, one with a dynamic content and another with the static, but it isn't like that, is it? thanks, Pedro Salazar. On Thu, 2003-01-16 at 17:50, Turner, John wrote: I can't explain those log messages. I do know that mod_jk uses a single file called workers.properties. I believe, if you use the JkWorkersFile command in httpd.conf, that you can tell mod_jk to use any file you like, like my.properties. So, if you want to use jk2.properties, you probably can. I only use mod_jk, and I can assure you I have no files named jk2.properties. mod_jk2 is a completely different module. It takes different configuration commands, it uses two files instead of one (or can use a single file if you use JkUriSet in httpd.conf). So, the confusion can be clarified by you telling us which module you are using: JK (mod_jk), or JK2 (mod_jk2). Then we can help you figure out your configuration questions, if any. Otherwise we are just going in circles. Regarding your question about the images: where are the images located relative to Apache and Tomcat? Does Tomcat have access to that directory? Does Apache have access to that directory? More information is needed. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:29 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x Greetings, John, if what you said is right why is that happens: 1)when my tomcat starts, it logs a message saying the configuration is the jk.properties: 25984 [main] INFO http11.Http11Protocol - Starting Coyote HTTP/1.1 on port 8080 26167 [main] INFO common.ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 26278 [main] INFO server.JkMain - Jk running ID=0 time=3/294 config=/opt/tomcat/conf/jk2.properties is it also using the workers.properties? (is this the name to use?) 2)and not touching in any apache configuration (pointing to tomcat's workers.properties), the Apj13Connector works just fine, but the CoyoteConnector doesn't log any message in log file! Could you figure why? thanks Pedro Salazar. PS. With my Apj13Connector (the only one I could put it to work yet), accessing the http://localhost/index.jsp (I have a mapping JkMount /*.jsp ajp13), the images don't appear in the default web page of tomcat. Why? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
Sorry, I'm just not clear what you are asking. Mod_jk uses workers.properties 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 -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 2:20 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x 1- About the Apache, I have no doubts that the mod_jk uses the file defined in JkWorkersFile directive. But, is that clear that Tomcat (4.1.x), I mean the CoyoteConnector, uses only and just only the workers.properties inside $TOMCAT_HOME/conf/? Or could it be in another place? I heard something about workers2.properties, another about conf/jk/workers.properties, I don't know if they were specific for apache or if the location can be defined. I would like to clarify this issue, I mean, the correct file name and location of the configuration of the workers to CoyoteConnector that should be the same for Apj13Connector. 2- About the images, they are located inside WAR files in webapps of tomcat. I tried to use JkAutoAlias /opt/tomcat/webapps but apparently it isn't a known directive of mod_jk (probably only to mod_jk2). So, I thought that by default any request of a image inside a JkMount context should be handled by Apache in transparent way. It appears that I should have a two web applications, one with a dynamic content and another with the static, but it isn't like that, is it? thanks, Pedro Salazar. On Thu, 2003-01-16 at 17:50, Turner, John wrote: I can't explain those log messages. I do know that mod_jk uses a single file called workers.properties. I believe, if you use the JkWorkersFile command in httpd.conf, that you can tell mod_jk to use any file you like, like my.properties. So, if you want to use jk2.properties, you probably can. I only use mod_jk, and I can assure you I have no files named jk2.properties. mod_jk2 is a completely different module. It takes different configuration commands, it uses two files instead of one (or can use a single file if you use JkUriSet in httpd.conf). So, the confusion can be clarified by you telling us which module you are using: JK (mod_jk), or JK2 (mod_jk2). Then we can help you figure out your configuration questions, if any. Otherwise we are just going in circles. Regarding your question about the images: where are the images located relative to Apache and Tomcat? Does Tomcat have access to that directory? Does Apache have access to that directory? More information is needed. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:29 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x Greetings, John, if what you said is right why is that happens: 1)when my tomcat starts, it logs a message saying the configuration is the jk.properties: 25984 [main] INFO http11.Http11Protocol - Starting Coyote HTTP/1.1 on port 8080 26167 [main] INFO common.ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 26278 [main] INFO server.JkMain - Jk running ID=0 time=3/294 config=/opt/tomcat/conf/jk2.properties is it also using the workers.properties? (is this the name to use?) 2)and not touching in any apache configuration (pointing to tomcat's workers.properties), the Apj13Connector works just fine, but the CoyoteConnector doesn't log any message in log file! Could you figure why? thanks Pedro Salazar. PS. With my Apj13Connector (the only one I could put it to work yet), accessing the http://localhost/index.jsp (I have a mapping JkMount /*.jsp ajp13), the images don't appear in the default web page of tomcat. Why? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
If I understand correctly, the CoyoteConnector was specifically written to take advantage of the features that exist within mod_jk2. As a result it loads a file JK2.properties. However since jk2 and jk both use ajp to talk to Tomcat, the default configuration jk2.properties with everything commented out allows the CoyoteConnector to accept request from an apache server using mod_jk. In many respect, the CoyoteConnector's ability to communicate with mod_jk if a bonus feature of the Connector as oppossed to its primary purpose in life which is to accept mod_jk2 requests. This philosophy of use is implied in the documentation located at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/confighowto.html On the other hand the ajp13Connector was written with mod_jk in mind. Jeff -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:30 PM To: 'Tomcat Users List' Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x Sorry, I'm just not clear what you are asking. Mod_jk uses workers.properties 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 -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 2:20 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x 1- About the Apache, I have no doubts that the mod_jk uses the file defined in JkWorkersFile directive. But, is that clear that Tomcat (4.1.x), I mean the CoyoteConnector, uses only and just only the workers.properties inside $TOMCAT_HOME/conf/? Or could it be in another place? I heard something about workers2.properties, another about conf/jk/workers.properties, I don't know if they were specific for apache or if the location can be defined. I would like to clarify this issue, I mean, the correct file name and location of the configuration of the workers to CoyoteConnector that should be the same for Apj13Connector. 2- About the images, they are located inside WAR files in webapps of tomcat. I tried to use JkAutoAlias /opt/tomcat/webapps but apparently it isn't a known directive of mod_jk (probably only to mod_jk2). So, I thought that by default any request of a image inside a JkMount context should be handled by Apache in transparent way. It appears that I should have a two web applications, one with a dynamic content and another with the static, but it isn't like that, is it? thanks, Pedro Salazar. On Thu, 2003-01-16 at 17:50, Turner, John wrote: I can't explain those log messages. I do know that mod_jk uses a single file called workers.properties. I believe, if you use the JkWorkersFile command in httpd.conf, that you can tell mod_jk to use any file you like, like my.properties. So, if you want to use jk2.properties, you probably can. I only use mod_jk, and I can assure you I have no files named jk2.properties. mod_jk2 is a completely different module. It takes different configuration commands, it uses two files instead of one (or can use a single file if you use JkUriSet in httpd.conf). So, the confusion can be clarified by you telling us which module you are using: JK (mod_jk), or JK2 (mod_jk2). Then we can help you figure out your configuration questions, if any. Otherwise we are just going in circles. Regarding your question about the images: where are the images located relative to Apache and Tomcat? Does Tomcat have access to that directory? Does Apache have access to that directory? More information is needed. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:29 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x Greetings, John, if what you said is right why is that happens: 1)when my tomcat starts, it logs a message saying the configuration is the jk.properties: 25984 [main] INFO http11.Http11Protocol - Starting Coyote HTTP/1.1 on port 8080 26167 [main] INFO common.ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 26278 [main] INFO server.JkMain - Jk running ID=0
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
Thanks for the clarification. John -Original Message- From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 2:55 PM To: 'Tomcat Users List' Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x If I understand correctly, the CoyoteConnector was specifically written to take advantage of the features that exist within mod_jk2. As a result it loads a file JK2.properties. However since jk2 and jk both use ajp to talk to Tomcat, the default configuration jk2.properties with everything commented out allows the CoyoteConnector to accept request from an apache server using mod_jk. In many respect, the CoyoteConnector's ability to communicate with mod_jk if a bonus feature of the Connector as oppossed to its primary purpose in life which is to accept mod_jk2 requests. This philosophy of use is implied in the documentation located at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/config howto.html On the other hand the ajp13Connector was written with mod_jk in mind. Jeff -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
clear OK, I wasn't clear about the workers.properties. 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, workers.properties only have meaning to apache! I'm clear now, thanks! /clear two-more-things one 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? /one two So, what could be wrong when I use the CoyoteConnector? The workers.properties should be the same as for the Apj13Connector, and it works with me! /two /two-more-thing On Thu, 2003-01-16 at 19:29, Turner, John wrote: Sorry, I'm just not clear what you are asking. Mod_jk uses workers.properties 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: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x
1 - you can go either way. On my systems, there are separate Tomcats, each with one Connector. Others do it differently. John -Original Message- From: Pedro Salazar [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 3:18 PM To: Tomcat Users List Subject: RE: configure CoyoteConnector with mod_jk in tomcat 4.1.x clear OK, I wasn't clear about the workers.properties. 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, workers.properties only have meaning to apache! I'm clear now, thanks! /clear two-more-things one 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? /one two So, what could be wrong when I use the CoyoteConnector? The workers.properties should be the same as for the Apj13Connector, and it works with me! /two /two-more-thing -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
