users@grizzly.java.net

Re: Unblocking keep-alive exception - java.lang.NullPointerException

From: Oleksiy Stashok <oleksiy.stashok_at_oracle.com>
Date: Mon, 19 Sep 2011 11:50:28 +0200

Hi,

can you pls. check if the same is reproducible with Grizzly 1.0.40?


Thanks.

WBR,
alexey.

On 09/16/2011 04:14 PM, rosa wrote:
>
> Hello,
>
> We´re running an application under glassfish 2.1 and the following
> libraries:
>
> * dwr.jar (3RC2)
>
> * grizzly-framework-http-1.0.34.jar
>
> * grizzly-continuation-1.8.6.jar
>
> Our problem is that sometimes we have this exception:
>
> [#|2011-09-16T16:37:56.533+0200|SEVERE|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=21;_ThreadName=httpSSLWorkerThread-8082-19;_RequestID=2568afe1-ac05-4c29-a30d-201160c82c90;|WEB0777:
> Unblocking keep-alive exception
> java.lang.NullPointerException
> at
> com.sun.enterprise.web.connector.grizzly.ByteBufferInputStream.read(ByteBufferInputStream.java:164)
> at
> org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:747)
> at
> org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:418)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.parseRequest(DefaultProcessorTask.java:736)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.parseRequest(DefaultProcessorTask.java:699)
> at
> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.preExecute(DefaultAsyncExecutor.java:146)
> at
> com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:88)
> at
> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
> |#]
>
> [#|2011-09-16T16:38:06.656+0200|SEVERE|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=22;_ThreadName=httpSSLWorkerThread-8082-9;_RequestID=67362d2e-4d57-496d-a145-a0605a2af307;|The
> log message is null.
> java.lang.NullPointerException
> at
> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.registerKey(DefaultReadTask.java:438)
> at
> com.sun.enterprise.web.connector.grizzly.AsyncReadTask.terminate(AsyncReadTask.java:182)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.taskEvent(DefaultReadTask.java:365)
> at
> com.sun.enterprise.web.connector.grizzly.TaskBase.fireTaskEvent(TaskBase.java:234)
> at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.terminateProcess(DefaultProcessorTask.java:856)
> at
> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.postExecute(DefaultAsyncExecutor.java:206)
> at
> com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:99)
> at
> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
> |#]
>
>
> This exception makes that a “Incomplete response from server” message shows
> up in ours browsers.
>
> Could you help us please? Thanks in advance
> Rosa
>
>
>
>
>
>
>
> --
> View this message in context: http://grizzly.1045725.n5.nabble.com/Unblocking-keep-alive-exception-java-lang-NullPointerException-tp4810846p4810846.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.