On 15/05/2013 20:35, Rossen Stoyanchev wrote:
Mark,
While there is no response on the Servlet spec list, I have some follow-up
questions:
If you call complete() you'll end up with an IllegalStateException when
the error handler kicks in. You have to use dispatch(). The error handle
kicks
Mark,
While there is no response on the Servlet spec list, I have some follow-up
questions:
If you call complete() you'll end up with an IllegalStateException when
the error handler kicks in. You have to use dispatch(). The error handle
kicks in as soon as the dispatch() tries to write to the
: Mark Thomas ma...@apache.org To: Tomcat Users List
users@tomcat.apache.org Sent: Sunday, May 5, 2013 11:35:54 AM
Subject: Re: IOException from the response during an async request
From what I can see to complete the async request in this (or
any async scenario) one has to call
When a request has been put into async mode (via request.startAsync), the
response may remain open long after the initial container thread has exited.
Meanwhile a non-container thread is allowed to write to the response but if an
IOException occurs, there is obviously no way to report it to
On 05/05/2013 13:18, Rossen Stoyanchev wrote:
When a request has been put into async mode (via request.startAsync),
the response may remain open long after the initial container thread
has exited. Meanwhile a non-container thread is allowed to write to
the response but if an IOException
- Original Message -
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, May 5, 2013 11:35:54 AM
Subject: Re: IOException from the response during an async request
From what I can see to complete the async request in this (or any
async
On 05/05/2013 17:29, Rossen Stoyanchev wrote:
- Original Message -
From: Mark Thomas ma...@apache.org To: Tomcat Users List
users@tomcat.apache.org Sent: Sunday, May 5, 2013 11:35:54 AM
Subject: Re: IOException from the response during an async request
From what I can see
