RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.
The hosts file is now correct. I'm now able to load the /examples directory the following ways: http://w121c20.legacyhs:8080/examples http://w121c20.legacyhs/examples but not with http://localhost:8080/examples or http://localhost/examples Also, when I test a jsp example as standalone, it works fine (http://w121c20.legacyhs:8080/examples/jsp/num/numguess.jsp) but not when I remove the port 8080 from the URL: http://w121c20.legacyhs/examples/jsp/num/numguess.jsp The only strange config problem was that jk directory under CATALINA_HOME/conf didn't exist prior to me creating the workers.properties file! I'm not sure if this meaningful. Suggestions anyone? -Original Message- From: Josh G [mailto:josh;gfunk007.com] Sent: Wednesday, October 30, 2002 5:37 PM To: Tomcat Users List Subject: Re: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error. You don't have localhost in your HOSTS file, add this entry and it'll all be good :) -Josh Who can it be knocking at my door? Go away, don't come round here no more. Can't you see that it's late at night? I'm very tired, and I'm not feeling right. - Original Message - From: Lambert, Stephen : CO IR [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, October 31, 2002 11:20 AM Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error. John, I still can't get this to work?! I started over from scratch with your docs and was able correct the duplicate mod_jk.conf problem. However, when I try the following URL's, localhost still doesn't work. http://localhost result= Netscape starts searching the internet http://localhost:8080 result= Netscape starts searching the internet http://w121c20.legacyhs:8080 result= works fine! http://w121c20.legacyhs result= works fine! Is this a Netscape issue? -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Tuesday, October 08, 2002 5:34 AM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Take a look at the docs for the ApacheConfig Listener...there are parameters there to stop things like appending to mod_jk.conf, which might be what is happening. In other words, shut everything down, wait a bit, delete mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct (make sure permissions on mod_jk.conf file are correct, too...the user Tomcat is running as should have write/delete access to that file). It's possible that you just keep using the same mod_jk.conf file, a new one may not be getting written everytime Tomcat starts. For the 8080 message, make sure you have a HTTP connector on 8080 enabled in server.xml. Take a second and go back through my HOWTO (not the connector build steps). There are only 4 or 5 specific changes to make to httpd.conf and server.xml to get Apache working with Tomcat...and none of those changes are major. John -Original Message- -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.
John, I still can't get this to work?! I started over from scratch with your docs and was able correct the duplicate mod_jk.conf problem. However, when I try the following URL's, localhost still doesn't work. http://localhost result= Netscape starts searching the internet http://localhost:8080 result= Netscape starts searching the internet http://w121c20.legacyhs:8080 result= works fine! http://w121c20.legacyhs result= works fine! Is this a Netscape issue? -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Tuesday, October 08, 2002 5:34 AM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Take a look at the docs for the ApacheConfig Listener...there are parameters there to stop things like appending to mod_jk.conf, which might be what is happening. In other words, shut everything down, wait a bit, delete mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct (make sure permissions on mod_jk.conf file are correct, too...the user Tomcat is running as should have write/delete access to that file). It's possible that you just keep using the same mod_jk.conf file, a new one may not be getting written everytime Tomcat starts. For the 8080 message, make sure you have a HTTP connector on 8080 enabled in server.xml. Take a second and go back through my HOWTO (not the connector build steps). There are only 4 or 5 specific changes to make to httpd.conf and server.xml to get Apache working with Tomcat...and none of those changes are major. John -Original Message- From: Lambert, Stephen : CO IR [mailto:SLambert;LHS.ORG] Sent: Monday, October 07, 2002 7:31 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Changes below completed. Apache now starts with no warning! However, result of http://localhost:8080/examples is unable to locate server localhost:8080 And result of http://localhost/examples finds the jsp examples with a URL of http://w121c20.legacyhs/examples/ What's bizarre is that the mod_jk.conf file is once again populated with a second VirtualHost directive after starting Tomcat. So if I stop/start Tomcat/Apache the VirtualHost warning message re-appears. Stephen. -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Monday, October 07, 2002 3:08 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . In your server.xml, change the defaultHost parameter of your Engine element to localhost. You're getting that Apache error because you have two VirtualHost definitions for w121c20.legacyhs in mod_jk.conf. There should only be one. Also, change ServerName in httpd.conf to w121c20.legacyhs. Give that a try, and see what happens. John -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error.
You don't have localhost in your HOSTS file, add this entry and it'll all be good :) -Josh Who can it be knocking at my door? Go away, don't come round here no more. Can't you see that it's late at night? I'm very tired, and I'm not feeling right. - Original Message - From: Lambert, Stephen : CO IR [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, October 31, 2002 11:20 AM Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error. John, I still can't get this to work?! I started over from scratch with your docs and was able correct the duplicate mod_jk.conf problem. However, when I try the following URL's, localhost still doesn't work. http://localhost result= Netscape starts searching the internet http://localhost:8080 result= Netscape starts searching the internet http://w121c20.legacyhs:8080 result= works fine! http://w121c20.legacyhs result= works fine! Is this a Netscape issue? -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Tuesday, October 08, 2002 5:34 AM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Take a look at the docs for the ApacheConfig Listener...there are parameters there to stop things like appending to mod_jk.conf, which might be what is happening. In other words, shut everything down, wait a bit, delete mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct (make sure permissions on mod_jk.conf file are correct, too...the user Tomcat is running as should have write/delete access to that file). It's possible that you just keep using the same mod_jk.conf file, a new one may not be getting written everytime Tomcat starts. For the 8080 message, make sure you have a HTTP connector on 8080 enabled in server.xml. Take a second and go back through my HOWTO (not the connector build steps). There are only 4 or 5 specific changes to make to httpd.conf and server.xml to get Apache working with Tomcat...and none of those changes are major. John -Original Message- From: Lambert, Stephen : CO IR [mailto:SLambert;LHS.ORG] Sent: Monday, October 07, 2002 7:31 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Changes below completed. Apache now starts with no warning! However, result of http://localhost:8080/examples is unable to locate server localhost:8080 And result of http://localhost/examples finds the jsp examples with a URL of http://w121c20.legacyhs/examples/ What's bizarre is that the mod_jk.conf file is once again populated with a second VirtualHost directive after starting Tomcat. So if I stop/start Tomcat/Apache the VirtualHost warning message re-appears. Stephen. -Original Message- From: Turner, John [mailto:JTurner;AAS.com] Sent: Monday, October 07, 2002 3:08 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . In your server.xml, change the defaultHost parameter of your Engine element to localhost. You're getting that Apache error because you have two VirtualHost definitions for w121c20.legacyhs in mod_jk.conf. There should only be one. Also, change ServerName in httpd.conf to w121c20.legacyhs. Give that a try, and see what happens. John -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error .
Take a look at the docs for the ApacheConfig Listener...there are parameters there to stop things like appending to mod_jk.conf, which might be what is happening. In other words, shut everything down, wait a bit, delete mod_jk.conf, then start up Tomcat and see if the mod_jk.conf file is correct (make sure permissions on mod_jk.conf file are correct, too...the user Tomcat is running as should have write/delete access to that file). It's possible that you just keep using the same mod_jk.conf file, a new one may not be getting written everytime Tomcat starts. For the 8080 message, make sure you have a HTTP connector on 8080 enabled in server.xml. Take a second and go back through my HOWTO (not the connector build steps). There are only 4 or 5 specific changes to make to httpd.conf and server.xml to get Apache working with Tomcat...and none of those changes are major. John -Original Message- From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 7:31 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error . Changes below completed. Apache now starts with no warning! However, result of http://localhost:8080/examples is unable to locate server localhost:8080 And result of http://localhost/examples finds the jsp examples with a URL of http://w121c20.legacyhs/examples/ What's bizarre is that the mod_jk.conf file is once again populated with a second VirtualHost directive after starting Tomcat. So if I stop/start Tomcat/Apache the VirtualHost warning message re-appears. Stephen. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 3:08 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . In your server.xml, change the defaultHost parameter of your Engine element to localhost. You're getting that Apache error because you have two VirtualHost definitions for w121c20.legacyhs in mod_jk.conf. There should only be one. Also, change ServerName in httpd.conf to w121c20.legacyhs. Give that a try, and see what happens. John -Original Message- From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 5:58 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 2:50 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . Post your httpd.conf, and mod_jk.conf if your JK commands are not in httpd.conf. John -- 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: tomcat 4.1.12 with apache1.3.26 and mod_jk integration error .
Changes below completed. Apache now starts with no warning! However, result of http://localhost:8080/examples is unable to locate server localhost:8080 And result of http://localhost/examples finds the jsp examples with a URL of http://w121c20.legacyhs/examples/ What's bizarre is that the mod_jk.conf file is once again populated with a second VirtualHost directive after starting Tomcat. So if I stop/start Tomcat/Apache the VirtualHost warning message re-appears. Stephen. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 3:08 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . In your server.xml, change the defaultHost parameter of your Engine element to localhost. You're getting that Apache error because you have two VirtualHost definitions for w121c20.legacyhs in mod_jk.conf. There should only be one. Also, change ServerName in httpd.conf to w121c20.legacyhs. Give that a try, and see what happens. John -Original Message- From: Lambert, Stephen : CO IR [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 5:58 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 2:50 PM To: 'Tomcat Users List' Subject: RE: tomcat 4.1.12 with apache1.3.26 and mod_jk intergration error . Post your httpd.conf, and mod_jk.conf if your JK commands are not in httpd.conf. John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
