users@grizzly.java.net

Re: Problems with pipelining requests

From: Patrick Julien <pjulien_at_gmail.com>
Date: Mon, 15 Dec 2008 15:08:22 -0500

>
>
> So far so good. Can you add content=length=<<lenght of the above message" to
> see if that help? Also can you send me a jstack PID when the "lock" happens?
> I'm pretty usre the parser is waiting for more bytes.


Originally, I did have this header in with the same results. However,
just to be clear, its value was always set to zero since this header
represents the number of bytes of the entity body, not the headers.
Here, indeed, the body was always empty.


>
> Add -Dcom.sun.enterprise.web.connector.grizzly.snoopEnabled=true and send
> the log here. But I doubt you will find http pipelining support with Tomcat
> (the parser code here is from them)...I think Jetty might work, but I'm
> clearly not sure....


I did have this property set also, I knew of this property because of
a prior conservation we had on another issue. However, other than
showing headers, this did not log anything.

I will work on getting a stack snapshot from glassfish using jstack.