Hi David,
just to make sure, does everything work fine with 1.9.37-SNAPSHOT?
Thanks.
Alexey.
On 07/06/2011 10:50 AM, Gay David (Annecy) wrote:
>
> Oups, bad info : I just reproduce the same errors with Grizzly 1.9.36
>
> Regards
>
> David
>
> *De :*Gay David (Annecy) [mailto:dgay_at_axway.com]
> *Envoyé :* mercredi 6 juillet 2011 10:47
> *À :* users_at_grizzly.java.net
> *Objet :* RE: Grizzly Suspend
>
> Hi Alexey,
>
> Thanks for your quick reply and fix.
>
> I manage to checkout the trunk : I had to fight a little bit with GIT,
> cause it's pretty new for me, but it's ok now :-)
>
> Unfortunately, I still have the error "Invalid chunk header" error in
> my application server.
>
> So, I modify the test to better reflect what is done : you can see
> that it mix simple Adapter and GrizzlyAdapter.
>
> That's the case in the application server.
>
> When I run this test against the 1.9.37-SNAPSHOT I see these errors :
>
> GRAVE: GRIZZLY0040: Request header is too large.
>
> java.nio.BufferOverflowException
>
> at
> com.sun.grizzly.tcp.http11.InternalInputBuffer.fill(InternalInputBuffer.java:765)
>
> at
> com.sun.grizzly.tcp.http11.InternalInputBuffer.parseHeader(InternalInputBuffer.java:615)
>
> at
> com.sun.grizzly.tcp.http11.InternalInputBuffer.parseHeaders(InternalInputBuffer.java:555)
>
> at
> com.sun.grizzly.http.ProcessorTask.parseRequest(ProcessorTask.java:881)
>
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:692)
>
> at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1022)
>
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
>
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
>
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>
> and
>
> GRAVE: GRIZZLY0051: ProcessorTask exception.
>
> java.lang.NullPointerException
>
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.setSelectionKey(SocketChannelOutputBuffer.java:211)
>
> at
> com.sun.grizzly.http.ProcessorTask.postProcess(ProcessorTask.java:966)
>
> at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1023)
>
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
>
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
>
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
>
> at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
>
> at java.lang.Thread.run(Thread.java:662)
>
> It's still not my "Invalid chunk header" but, it may be related ?
>
> Is there a problem in my code here ?
>
> BTW : I try to re-run this test against 1.9.36 several times, without
> seeing any problem (even if I still have the "Invalid chunk header" in
> my server)
>
> Thanks again for your help
>
> Regards
>
> David
>
> *De :*Oleksiy Stashok [mailto:oleksiy.stashok_at_oracle.com]
> *Envoyé :* lundi 4 juillet 2011 16:07
> *À :* users_at_grizzly.java.net
> *Objet :* Re: Grizzly Suspend
>
> Hi David,
>
> thanks a lot for the testcase!
> We've fixed it [1] on the trunk. Fix is going to be available in the
> next 1.9.37 release.
>
> Thanks.
>
> WBR,
> Alexey.
>
> [1] http://java.net/jira/browse/GRIZZLY-1035
>
> ...
>