Rsync
Tweet
JSP pages shows 404 error, even though the Apache Tomcat was auto-configured from WHM
Apache Tomcat was auto-configured from WHM installation on VPS, but getting 404 with jsp pages.
PROBLEM
Apache Web Server was not passing servlet requests to Apache Tomcat and JSP pages show 404 errors.
CAUSE
This was occurring because Tomcat could not read from the "public_html" directory for the site.
This was a result of file protect being enabled in easyapache. This option causes all public_html directories to be owned by the user and the group "nobody", leaving all other users unable to index those directories. Unfortunately this leaves "tomcat", which runs as the user "tomcat", unable to access those files as well.
Solution
It should be addressed by executing following script.
Now Restart Tomcat service
Now, your "jsp" pages work fine.
PROBLEM
Apache Web Server was not passing servlet requests to Apache Tomcat and JSP pages show 404 errors.
CAUSE
This was occurring because Tomcat could not read from the "public_html" directory for the site.
This was a result of file protect being enabled in easyapache. This option causes all public_html directories to be owned by the user and the group "nobody", leaving all other users unable to index those directories. Unfortunately this leaves "tomcat", which runs as the user "tomcat", unable to access those files as well.
Solution
It should be addressed by executing following script.
/scripts/disablefileprotect
/scripts/restartsrv_tomcat