Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation
Written by Jahangir on November 8, 2008 – 12:31 am -Error
Apache Web Server was not passing servlet requests to Apache Tomcat. It served 404 errors to jsp pages, even though the Apache Tomcat was auto-configured by the WHM / Cpanel installation.
SEVERE: Error starting static Resources java.lang.IllegalArgumentException: Document base ççç does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:141)
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
Restart Tomcat service
/scripts/restartsrv_tomcat
Issue Fixed, now “jsp” pages works fine.
Enjoy
Tags: .jsp pages not working, cpanel tomcat issue, jsp pages shows 404 error, tomcat enabled but jsp pages not working
Posted in Dedicated Server Hosting, Linux VPS Hosting |
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Del.icio.us Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Del.icio.us](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/delicious.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To digg Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To digg](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/digg.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To FURL Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To FURL](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/furl.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To reddit Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To reddit](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/reddit.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Technorati Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Technorati](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/technorati.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Yahoo My Web Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Yahoo My Web](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/yahoo_myweb.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Stumble Upon Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Stumble Upon](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/stumbleupon.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Google Bookmarks Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Google Bookmarks](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/google.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Netscape Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Netscape](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/netscape.gif)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Ask Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Ask](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/ask.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Live-MSN Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Live-MSN](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/live.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To FaceBook Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To FaceBook](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/facebook.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To MySpace Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To MySpace](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/myspace.png)
![Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Social Bookmarking Reloaded Add 'Getting 404 error to “jsp” pages, even though Tomcat was auto-configured by [WHM/cPanel] installation' To Social Bookmarking Reloaded](http://trulymanaged.com/blog/wp-content/plugins/social-bookmarking-reloaded/sbr.png)





