On 05/05/2013 17:29, Rossen Stoyanchev wrote:
>
> - Original Message -
>> From: "Mark Thomas" To: "Tomcat Users List"
>> 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
- Original Message -
> From: "Mark Thomas"
> To: "Tomcat Users List"
> 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 a
On 05/05/2013 16:56, Jesse Barnum wrote:
> I thought that the purpose of having elements in the
> context.xml file was so that end users and server administrators
> could easily customize the application behavior of a deployed
> application.
Correct.
> If that's true, then why is the context.xml
I thought that the purpose of having elements in the context.xml
file was so that end users and server administrators could easily customize the
application behavior of a deployed application.
If that's true, then why is the context.xml file no longer extracted in Tomcat
7? Leaving it in the a
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
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 the
Thanks!
- Original Message -
> From: "Mark Thomas"
> To: "Tomcat Users List"
> Sent: Saturday, May 4, 2013 5:57:15 PM
> Subject: Re: Status 204 (no content) and Content-Type header
>
> On 04/05/2013 21:21, Mark Thomas wrote:
> > On 04/05/2013 20:43, Rossen Stoyanchev wrote:
> >>
> >> I
