[jetty-discuss] [jira] Commented: (JETTY-329) NPE in HttpParser.isMoreInBuffer

[Sam P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/JETTY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99043 ] 

Sam Pullara commented on JETTY-329:
-----------------------------------

Forgot to mention this was on Mac OS X, JDK 1.5.

> NPE in HttpParser.isMoreInBuffer
> --------------------------------
>
>                 Key: JETTY-329
>                 URL: http://jira.codehaus.org/browse/JETTY-329
>             Project: Jetty
>          Issue Type: Bug
>          Components: NIO
>    Affects Versions: 6.1.2rc2
>         Environment: Windows Vista dual core.
>            Reporter: Anders Wallgren
>            Priority: Blocker
>         Attachments: HttpServerTest.java
>
>
> In trying to track down what we think is a buffer problem in Jetty, I ran across this NullPointerException while doing some stress testing with the testBufferProblem() test in the attached JUnit test (our copy of the HttpServerTest class).
> {code}
> 2007-04-30T18:58:11.698 | ERROR | btpool0-3     |                                               | log                            | handle failed
> java.lang.NullPointerException
> 	at org.mortbay.jetty.HttpParser.isMoreInBuffer(HttpParser.java:161)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:437)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
> 	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> {code}
> The last changed rev of HttpParser.java is 1727.  We've been taking from  the SVN tip to get bug fixes, so my 6.1.2rc label is definitely not a complete description of the state of the source, but it's the SVN head from sometime last week.
> I've seen one instance of this exception in many iterations of the testBufferProblem unit test, but it's worrisome, obviously.  We're trying to get a small test case for a problem where we see data from one request show up in the buffer being used for another request.

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