Tomcat v3.3b2 and mod_jk (again)
Larry Having got yesterday's setup to work, I thought I'd try to go one step further (having browsed some of the previous correspondence about mod_jk). Since sota and sota.silly.domain.net are the same site, I tried making apps-sota.xml as follows: Server Host name=sota alias name=sota.silly.domain.net / Context path= docBase=webapps/Sota / /Host /Server This gave me an auto-generated mod_jk.conf as follows: ## Auto generated on Fri Sep 07 12:28:23 BST 2001## IfModule !mod_jk.c LoadModule jk_module /usr/lib/apache/mod_jk.so /IfModule JkWorkersFile /opt/jakarta-tomcat-3.3-b2/conf/jk/workers.properties JkLogFile /opt/jakarta-tomcat-3.3-b2/logs/mod_jk.log JkLogLevel emerg JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /admin ajp13 JkMount /admin/* ajp13 JkMount /Sota ajp13 JkMount /Sota/* ajp13 JkMount / ajp13 JkMount /* ajp13 # To avoid Apache serving root welcome files from htdocs, update DocumentRoot # to point to: /opt/jakarta-tomcat-3.3-b2/webapps/ROOT NameVirtualHost * VirtualHost * ServerName sota JkMount / ajp13 JkMount /* ajp13 DocumentRoot /opt/jakarta-tomcat-3.3-b2/webapps/Sota /VirtualHost (no mention of sota.silly.domain.net) Now sota works, but sota.silly.domain.net doesn't (and sota.silly.domain.net:8080 just gives the default tomcat page). Any thoughts (or should I just go back to what I had before... Many thanks Mark
RE: Tomcat v3.3b2 and mod_jk (again)
Mark, Yes, there should be a mention of sota.silly.domain.net. Assuming an accurate cut and paste, try capitalizing the 'a' in alias ... and try again. The Alias approach does have the effect of mapping sota and sota.silly.domain.net to the same context. This could be seen as an advantage or disadvantage depending on your requirements. Cheers, Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 7:48 AM To: [EMAIL PROTECTED] Subject: Tomcat v3.3b2 and mod_jk (again) Larry Having got yesterday's setup to work, I thought I'd try to go one step further (having browsed some of the previous correspondence about mod_jk). Since sota and sota.silly.domain.net are the same site, I tried making apps-sota.xml as follows: Server Host name=sota alias name=sota.silly.domain.net / Context path= docBase=webapps/Sota / /Host /Server This gave me an auto-generated mod_jk.conf as follows: ## Auto generated on Fri Sep 07 12:28:23 BST 2001## IfModule !mod_jk.c LoadModule jk_module /usr/lib/apache/mod_jk.so /IfModule JkWorkersFile /opt/jakarta-tomcat-3.3-b2/conf/jk/workers.properties JkLogFile /opt/jakarta-tomcat-3.3-b2/logs/mod_jk.log JkLogLevel emerg JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /admin ajp13 JkMount /admin/* ajp13 JkMount /Sota ajp13 JkMount /Sota/* ajp13 JkMount / ajp13 JkMount /* ajp13 # To avoid Apache serving root welcome files from htdocs, update DocumentRoot # to point to: /opt/jakarta-tomcat-3.3-b2/webapps/ROOT NameVirtualHost * VirtualHost * ServerName sota JkMount / ajp13 JkMount /* ajp13 DocumentRoot /opt/jakarta-tomcat-3.3-b2/webapps/Sota /VirtualHost (no mention of sota.silly.domain.net) Now sota works, but sota.silly.domain.net doesn't (and sota.silly.domain.net:8080 just gives the default tomcat page). Any thoughts (or should I just go back to what I had before... Many thanks Mark
Re: Tomcat v3.3b2 and mod_jk (again)
Larry It works fine!!! One more question (to which I should know the answer): I need the classes in postgresql.jar for my JDBC Realms login - is there a directory under TOMCAT_HOME where I should put the file, or is it best just to leave it in my CLASSPATH? Many thanks for your help. Mark - Original Message - From: Larry Isaacs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 07, 2001 12:56 PM Subject: RE: Tomcat v3.3b2 and mod_jk (again) Mark, Yes, there should be a mention of sota.silly.domain.net. Assuming an accurate cut and paste, try capitalizing the 'a' in alias ... and try again. The Alias approach does have the effect of mapping sota and sota.silly.domain.net to the same context. This could be seen as an advantage or disadvantage depending on your requirements. Cheers, Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 7:48 AM To: [EMAIL PROTECTED] Subject: Tomcat v3.3b2 and mod_jk (again) Larry Having got yesterday's setup to work, I thought I'd try to go one step further (having browsed some of the previous correspondence about mod_jk). Since sota and sota.silly.domain.net are the same site, I tried making apps-sota.xml as follows: Server Host name=sota alias name=sota.silly.domain.net / Context path= docBase=webapps/Sota / /Host /Server This gave me an auto-generated mod_jk.conf as follows: ## Auto generated on Fri Sep 07 12:28:23 BST 2001## IfModule !mod_jk.c LoadModule jk_module /usr/lib/apache/mod_jk.so /IfModule JkWorkersFile /opt/jakarta-tomcat-3.3-b2/conf/jk/workers.properties JkLogFile /opt/jakarta-tomcat-3.3-b2/logs/mod_jk.log JkLogLevel emerg JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /admin ajp13 JkMount /admin/* ajp13 JkMount /Sota ajp13 JkMount /Sota/* ajp13 JkMount / ajp13 JkMount /* ajp13 # To avoid Apache serving root welcome files from htdocs, update DocumentRoot # to point to: /opt/jakarta-tomcat-3.3-b2/webapps/ROOT NameVirtualHost * VirtualHost * ServerName sota JkMount / ajp13 JkMount /* ajp13 DocumentRoot /opt/jakarta-tomcat-3.3-b2/webapps/Sota /VirtualHost (no mention of sota.silly.domain.net) Now sota works, but sota.silly.domain.net doesn't (and sota.silly.domain.net:8080 just gives the default tomcat page). Any thoughts (or should I just go back to what I had before... Many thanks Mark
RE: Tomcat v3.3b2 and mod_jk (again)
Mark, Both Tomcat 3.3, and I believe Tomcat 4.0 as well, ignore your CLASSPATH. They construct a classloader hierarchy more complicated than you typical application would use. As a result, some thought is required to place your classes in the appropriate classloader. The primary question is whether your classes should be visible to web applications, to the server classes, or both. For Tomcat 3.3, this is documented at: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_classes I haven't tried using a JDBCRealm, so off the top of my head, I can't say for certain where the proper location is. Since it is interacting with the JDBCRealm module, you might try putting postgresql.jar in the lib/container directory. If that doesn't work, try lib/common. Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Re: Tomcat v3.3b2 and mod_jk (again) Larry It works fine!!! One more question (to which I should know the answer): I need the classes in postgresql.jar for my JDBC Realms login - is there a directory under TOMCAT_HOME where I should put the file, or is it best just to leave it in my CLASSPATH? Many thanks for your help. Mark - Original Message - From: Larry Isaacs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 07, 2001 12:56 PM Subject: RE: Tomcat v3.3b2 and mod_jk (again) Mark, Yes, there should be a mention of sota.silly.domain.net. Assuming an accurate cut and paste, try capitalizing the 'a' in alias ... and try again. The Alias approach does have the effect of mapping sota and sota.silly.domain.net to the same context. This could be seen as an advantage or disadvantage depending on your requirements. Cheers, Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 7:48 AM To: [EMAIL PROTECTED] Subject: Tomcat v3.3b2 and mod_jk (again) Larry Having got yesterday's setup to work, I thought I'd try to go one step further (having browsed some of the previous correspondence about mod_jk). Since sota and sota.silly.domain.net are the same site, I tried making apps-sota.xml as follows: Server Host name=sota alias name=sota.silly.domain.net / Context path= docBase=webapps/Sota / /Host /Server This gave me an auto-generated mod_jk.conf as follows: ## Auto generated on Fri Sep 07 12:28:23 BST 2001## IfModule !mod_jk.c LoadModule jk_module /usr/lib/apache/mod_jk.so /IfModule JkWorkersFile /opt/jakarta-tomcat-3.3-b2/conf/jk/workers.properties JkLogFile /opt/jakarta-tomcat-3.3-b2/logs/mod_jk.log JkLogLevel emerg JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /admin ajp13 JkMount /admin/* ajp13 JkMount /Sota ajp13 JkMount /Sota/* ajp13 JkMount / ajp13 JkMount /* ajp13 # To avoid Apache serving root welcome files from htdocs, update DocumentRoot # to point to: /opt/jakarta-tomcat-3.3-b2/webapps/ROOT NameVirtualHost * VirtualHost * ServerName sota JkMount / ajp13 JkMount /* ajp13 DocumentRoot /opt/jakarta-tomcat-3.3-b2/webapps/Sota /VirtualHost (no mention of sota.silly.domain.net) Now sota works, but sota.silly.domain.net doesn't (and sota.silly.domain.net:8080 just gives the default tomcat page). Any thoughts (or should I just go back to what I had before... Many thanks Mark
Re: Tomcat v3.3b2 and mod_jk (again)
Larry Many thanks Mark - Original Message - From: Larry Isaacs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 07, 2001 1:27 PM Subject: RE: Tomcat v3.3b2 and mod_jk (again) Mark, Both Tomcat 3.3, and I believe Tomcat 4.0 as well, ignore your CLASSPATH. They construct a classloader hierarchy more complicated than you typical application would use. As a result, some thought is required to place your classes in the appropriate classloader. The primary question is whether your classes should be visible to web applications, to the server classes, or both. For Tomcat 3.3, this is documented at: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_ classes I haven't tried using a JDBCRealm, so off the top of my head, I can't say for certain where the proper location is. Since it is interacting with the JDBCRealm module, you might try putting postgresql.jar in the lib/container directory. If that doesn't work, try lib/common. Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Re: Tomcat v3.3b2 and mod_jk (again) Larry It works fine!!! One more question (to which I should know the answer): I need the classes in postgresql.jar for my JDBC Realms login - is there a directory under TOMCAT_HOME where I should put the file, or is it best just to leave it in my CLASSPATH? Many thanks for your help. Mark - Original Message - From: Larry Isaacs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 07, 2001 12:56 PM Subject: RE: Tomcat v3.3b2 and mod_jk (again) Mark, Yes, there should be a mention of sota.silly.domain.net. Assuming an accurate cut and paste, try capitalizing the 'a' in alias ... and try again. The Alias approach does have the effect of mapping sota and sota.silly.domain.net to the same context. This could be seen as an advantage or disadvantage depending on your requirements. Cheers, Larry -Original Message- From: Mark Muffett [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 7:48 AM To: [EMAIL PROTECTED] Subject: Tomcat v3.3b2 and mod_jk (again) Larry Having got yesterday's setup to work, I thought I'd try to go one step further (having browsed some of the previous correspondence about mod_jk). Since sota and sota.silly.domain.net are the same site, I tried making apps-sota.xml as follows: Server Host name=sota alias name=sota.silly.domain.net / Context path= docBase=webapps/Sota / /Host /Server This gave me an auto-generated mod_jk.conf as follows: ## Auto generated on Fri Sep 07 12:28:23 BST 2001## IfModule !mod_jk.c LoadModule jk_module /usr/lib/apache/mod_jk.so /IfModule JkWorkersFile /opt/jakarta-tomcat-3.3-b2/conf/jk/workers.properties JkLogFile /opt/jakarta-tomcat-3.3-b2/logs/mod_jk.log JkLogLevel emerg JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /admin ajp13 JkMount /admin/* ajp13 JkMount /Sota ajp13 JkMount /Sota/* ajp13 JkMount / ajp13 JkMount /* ajp13 # To avoid Apache serving root welcome files from htdocs, update DocumentRoot # to point to: /opt/jakarta-tomcat-3.3-b2/webapps/ROOT NameVirtualHost * VirtualHost * ServerName sota JkMount / ajp13 JkMount /* ajp13 DocumentRoot /opt/jakarta-tomcat-3.3-b2/webapps/Sota /VirtualHost (no mention of sota.silly.domain.net) Now sota works, but sota.silly.domain.net doesn't (and sota.silly.domain.net:8080 just gives the default tomcat page). Any thoughts (or should I just go back to what I had before... Many thanks Mark
