the connection
to tomcat if an error when writing back the answer to the client is
detected but not sure if such a behaviour can be configured for READ.
George
On Mon, Jan 22, 2018 at 11:45 AM, Emanuel Hategan <emanuel.hate...@gmail.com
> wrote:
> Hi Chris,
>
> > Forget
Hi Chris,
> Forget about EOFException, that was my mistake in the first email
> > (and subject). I'm interested in improved handling of aborted
> > connections (at least most of them). That's my end goal.
> >
> > read=-1 solely does not provide sufficient information to be able
> > to distinguish
Chris,
Emah,
>
> On 1/17/18 10:17 AM, emah wrote:
> > Chris,
> >
> >
> > Christopher Schultz-2 wrote
> >>> I'm running a tomcat 8.5.23 instance on ubuntu 16.04 (spring
> >>> boot application with embedded tomcat) configured with 2
> >>> connectors: Http11NioProtocol and AjpNioProtocol. The AJP
I'm running a tomcat 8.5.23 instance on ubuntu 16.04 (spring boot
application with embedded tomcat) configured with 2 connectors:
Http11NioProtocol and AjpNioProtocol.
The AJP one is accessed through an apache2 instance configured with
mod_jk.It all works well in the normal use case.
The
