Hello Chris, Thanks for your quick response. What you said makes sense to me but let me clarify my situation further.
> Hi, I changed port 8080 to 80 and I get page not found error. Please > note that I have another website that is running on an older version > of tomcat. What I mean here is that I have three 3 installations of tomcat not 2. There is tomcat 2.2 application (using port 80) that is being used for a very basic web page that has nothing but URLs to various parts of the application that is being run on Tomcat 6.0. This tomcat 6.0 application is running on port 8080. The older version of this application was using tomcat 4.1 and listening on port 8080 also. However, after upgrading the application to 6.0, I shutdown the tomcat 4.1 application. From the tomcat 2.2 homepage, I can just click the link that will take me directly to > http://localhost/MyWebAPP/ However, after shutting down tomcat 4.1, installing and configuring tomcat 6.0, I can use the new web app only using the following URL. http://localhost:8080/MyWebAPP/ Do I still need to do what you mentioned in your previous email or should there be a different approach. I can completely uninstall tomcat 4.1 if I have to. Thanks, Rashid >>> Christopher Schultz <ch...@christopherschultz.net> 4/7/2009 5:22 PM >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rashid, On 4/7/2009 5:08 PM, Rashid Malik wrote: > Hi, I changed port 8080 to 80 and I get page not found error. Please > note that I have another website that is running on an older version > of tomcat. Aah, you didn't mention that. Only one process may bind to a particular interface/port combination. In your case, port 80 is already taken (by Tomcat 4.1). If you want both Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put another piece of software out in front in order to play traffic cop and properly route the requests to the appropriate server (app on TC4.1 versus app on TC6.0). Apache httpd is a popular choice for accomplishing this. You will have to: 1. Change Tomcat 4.1's configuration so that the HTTP port is something /other/ than port 80 (8080 is a popular choice) 2. Change Tomcat 6.0's configuration so that the HTTP port is something /other/ than port 80 and 8080 (8081?) 3. Install Apache httpd and have it listen on port 80 4. Configure httpd to send the appropriate requests to the appropriate back-end server To accomplish #4, you will need to use either mod_proxy_http, mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a separate download). There is a lot of documentation for using mod_jk here: http://tomcat.apache.org/connectors-doc/ If you use mod_proxy_http, you'll need to do: ProxyPass /appA http://localhost:8080/appA ProxyPass /appB http://localhost:8081/appB That should be enough to get you started. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknbw/sACgkQ9CaO5/Lv0PA/TgCfUuclAcTXu9aQwp7Ov2qSK7I5 nacAoK2ple5RH6My3jwaTIeQBXB88caf =rcZe -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org