I am seeing NPEs after reloading a web application with a custom
<error-page>. Just downloaded the sample.war, added the following
block in web.xml and thus reloaded the web application:

    <error-page>
        <location>/404.jsp</location>
    </error-page>

Accessing a nonexisting page now results in NPE instead of error page
being shown.
After tomcat restart the error-page is shown, until the next reload of
the application:


10-Jul-2014 20:31:40.531 SEVERE [http-nio-8080-exec-2]
org.apache.catalina.core.StandardHostValve.custom Exception Processing
ErrorPage[errorCode=0, location=/404.jsp]
 java.lang.NullPointerException

at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:423)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:291)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:526)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1566)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1523)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

On Thu, Jul 10, 2014 at 4:53 PM, Mark Thomas <ma...@apache.org> wrote:
> The proposed Apache Tomcat 8.0.10 release is now available for voting.
>
> The main changes since 8.0.9 are:
> - Various improvements to the Mapper including fixing some concurrency
>   bugs
> - Update to Tomcat Native Library version 1.1.31 to pick up the Windows
>   binaries that are based on OpenSSL 1.0.1h
> - Start to add permessage-deflate to WebSocket. Currently only client
>   to server compression is supported.
>
> There is also the usual collection of bug fixes, new features and
> performance improvements. For full details, see the changelog:
> http://svn.us.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.10/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1017/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_10/
>
> The proposed 8.0.10 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 8.0.10
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to