tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Claver <kcla...@yahoo.com>
Subject Re: error-page for http 500 error code does not work
Date Fri, 03 Jun 2011 13:43:17 GMT
Thanks for the quick reply!

I zipped the tomcat install and deployed it to my Win 7 machine where it works without issue.

When the custom error servlet fails to display, I get the stock tomcat http 500 error page.

If I look at the access log, I see the 500 error:

192.168.xxx.xxx - - [02/Jun/2011:13:53:14 -0600] "POST /HMAApp/faces/main/TaskSearchTab.jsp
HTTP/1.0" 500 1000

I also see the com.sun.rave.web.ui.appbase.ApplicationException and java.lang.NullPointerException
in the localhost log file (both of which are set to display the custom error page in the application
specific web.xml):

Jun 2, 2011 1:53:14 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet Faces Servlet threw exception
com.sun.rave.web.ui.appbase.ApplicationException
        at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.cleanup(ViewHandlerImpl.java:559)
        at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:276)
        at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)
        at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
        at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
        at com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:198)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:581)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
        at hmaapp.utilmanagement.OPProcMain.prerender(OPProcMain.java:2355)
        at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.prerender(ViewHandlerImpl.java:771)
        at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:268)
        ... 22 more



---------------------------------


On 02/06/2011 21:45, Kevin Claver wrote:
> Two things I would like to note:
>=20
> 1.  When I invoke the Java HMAExceptionHandlerServlet configured to be =
used in the error-page block in the application specific web.xml directly=
 from the URL in the browser, it works.
>=20
> 2.  Tomcat 5.5.33 does correctly redirect to the error-page when runnin=
g on a Windows 7 machine.  The only time I have an issue is on the Linux =
configuration above.

The first things I'd check is whether there's something different about
your Tomcat installation on Linux.

You can ZIP the whole Tomcat install (including the app(s), if they're
in tomcat/webapps) and transfer the file & unzip on your Linux install.
 Start it up & see if the same thing happens.


Also: what error do you see, when the custom error servlet/page fails to
display?  Is it the same error as you expect or a different one?

- if an NPE occurs in your app, do you see a 500 + NPE stacktrace?
- or if a 500 occurs, do you see a 404?


p

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message