Patrick Julien wrote:
>>> 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....
>
>
> Wait a minute, that doesn't compute for me. Both glassfish and Tomcat
> documentation refer to pipelining via the "maxKeepAliveRequests"
> property.
>
> You can see it in the documentation of Tomcat here:
>
> http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
>
> and for glassfish, here:
>
> http://docs.sun.com/app/docs/doc/820-4507/abhco?a=view
OK...http pipelining is not what I means :-) Http pipelining usually
refer to the ability to sent multiple requests without waiting for the
response. So you can send R1,R2,R3 in one chunk and then wait for un
ordered response. I was under the impression you were talking about that
behavior.
What you mean here based on the above link is the maximum number of
requests a client can do on an open connection. The client does R1, wait
for Res1, then Req2, wait for Req2, etc.
Now I understand your issue. I think your request is invalid and Grizzly
is waiting for more bytes. Is the snippet you wrote previously contains
the entire request? I will try to reproduce the issue using that one and
telnet.
A+
-- jeanfrancois
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>