[jboss-jira] [JBoss JIRA] Resolved: (JBWEB-77) Servlet throws NPE the first time it is hit.

Remy Maucherat (JIRA) jira-events at lists.jboss.org
Tue Apr 3 08:43:58 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBWEB-77?page=all ]

Remy Maucherat resolved JBWEB-77.
---------------------------------

    Resolution: Done

I ported the trivial patch which fixes this NPE. However, using the print method of the servlet OS is a very bad idea overall, you should most likely be using a writer instead.

> Servlet throws NPE the first time it is hit.
> --------------------------------------------
>
>                 Key: JBWEB-77
>                 URL: http://jira.jboss.com/jira/browse/JBWEB-77
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Phillip Thurmond
>         Assigned To: Mladen Turk
>            Priority: Blocker
>         Attachments: TestServlet.war.zip
>
>
> The first time a servlet is hit, it throws a NPE.  After the exception is thrown, the servlet works correctly.  Here is the stack trace.  Example war attached.
> java.lang.NullPointerException
>         at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:471)
>         at org.apache.catalina.connector.CoyoteOutputStream.print(CoyoteOutputStream.java:113)
>         at test.TestServlet.doGet(TestServlet.java:67)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
>         at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list