Based on Mark Thomas' recommendation in another thread, I've upgraded to tomcat
7.0.11 and the issues I was seeing seem to be fixed.
This seems to be the relevant changelog entry:
"Fix issues that prevented asynchronous servlets from working when used with
the HTTP APR connector on platforms tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/11/2011 4:45 PM, André Warnier wrote:
> Chris wrote:
>> 1. Yes, tomcat is sending the header: "Transfer-Encoding: chunked"
>> 2. I've also tried using close() instead of flush() and I've seen the
>> same chunked encoding.
>> 3. The nginx r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/11/2011 10:19 AM, Chris wrote:
> 1. Yes, tomcat is sending the header: "Transfer-Encoding: chunked"
Okay. Does that happen even for HTTP 1.0? Is so, that looks like a spec
violation to me.
> 2. I've also tried using close() instead of fl
Chris wrote:
1. Yes, tomcat is sending the header: "Transfer-Encoding: chunked"
2. I've also tried using close() instead of flush() and I've seen the same
chunked encoding.
3. The nginx reverse proxying with the HttpProxyModule only supports HTTP/1.0 according
to the "Synopsis" section here: ht
1. Yes, tomcat is sending the header: "Transfer-Encoding: chunked"
2. I've also tried using close() instead of flush() and I've seen the same
chunked encoding.
3. The nginx reverse proxying with the HttpProxyModule only supports HTTP/1.0
according to the "Synopsis" section here: http://wiki.nginx
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/10/2011 12:37 PM, Chris wrote:
> As I mentioned below, the "0\r\n\r\n" was not being sent to nginx, although
> it was being sent to curl. The difference was that nginx was doing a GET
> HTTP/1.0, while curl was using HTTP/1.1. If I conf
I should also mention that I'm doing Servlet 3.0 async requests:
AsyncContext context= req.startAsync();
...
context.complete();
I've also tried using AJP instead of HTTP between tomcat and nginx, and I see
similar behaviour; tomcat doesn't terminate the reply when using APR.
Anyone have any ide
I've narrowed this down even further.
As I mentioned below, the "0\r\n\r\n" was not being sent to nginx, although it
was being sent to curl. The difference was that nginx was doing a GET HTTP/1.0,
while curl was using HTTP/1.1. If I configure curl to use HTTP/1.0 then I get
the same result: no
Hi All,
Yesterday I created bug 50906 for this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50906
Since then I've got some more details to add:
- I'm running with nginx in front of tomcat
- The 60 second timeout is happening in nginx and not tomcat
- Regardless of whether or not I'm
On 09/03/2011 21:49, Chris wrote:
> Hi,
> I'm using Tomcat 7.0.8 on Ubuntu 10.10.
>
> When using the APR based Tomcat Native Library (libtcnative), responses from
> Tomcat are being sent with a chunked encoding, but the "0" terminating the
> chunked response isn't sent until exactly 1 minute lat
Hi,
I'm using Tomcat 7.0.8 on Ubuntu 10.10.
When using the APR based Tomcat Native Library (libtcnative), responses from
Tomcat are being sent with a chunked encoding, but the "0" terminating the
chunked response isn't sent until exactly 1 minute later.
The response is being written to an
org.
11 matches
Mail list logo
