webapp works through Apache, not Tomcat directly
I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: webapp works through Apache, not Tomcat directly
Could be a permission issue: docBase=/usr/local/webserver/webapps/MyApp Tomcat is unable to read directory under =/usr/local/webserver/webserver. -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:44 PM To: Tomcat Users List Subject: webapp works through Apache, not Tomcat directly I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
Chakravarthy, Sundar wrote: Could be a permission issue: docBase=/usr/local/webserver/webapps/MyApp Tomcat is unable to read directory under =/usr/local/webserver/webserver. Both /usr/local/webserver/webapps where MyApp is located and $TOMCAT_HOME/webapps where examples are located are world readable: drwxr-xr-x Jerry -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:44 PM To: Tomcat Users List Subject: webapp works through Apache, not Tomcat directly I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
The symbolic link is to $TOMCAT_HOME (in /usr/local/webserver, I've defined symbolic links to both tomcat and apache: tomcat - jakarta.tomcat-4.1.27, and apache-apache_1.3.27), and Tomcat has no problem using it. It just won't run my webapp when called directly through port 8080. The webapp works fine when the request comes through Apache. It's still Tomcat that runs it and its servlet. Jerry Daniel Gibby wrote: Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
The linux equivalent of shared files is to make them world readable, which the webapp directory and all files in it are: drwxr-xr-x Still doesn't work. Jerry FRANCOIS Dufour wrote: FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
Are the files in a particular user's directory? I.E: /home/someUser On Tuesday 06 January 2004 09:28 pm, you wrote: The linux equivalent of shared files is to make them world readable, which the webapp directory and all files in it are: drwxr-xr-x Still doesn't work. Jerry FRANCOIS Dufour wrote: FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
No. /usr/local/webserver/webapps/MyApp Jerry Ben Souther wrote: Are the files in a particular user's directory? I.E: /home/someUser On Tuesday 06 January 2004 09:28 pm, you wrote: The linux equivalent of shared files is to make them world readable, which the webapp directory and all files in it are: drwxr-xr-x Still doesn't work. Jerry FRANCOIS Dufour wrote: FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
