RE: Response cut off after 10 seconds when using NIO2 connector

2017-07-13 Thread Matt Cosentino
: Tomcat Users List Subject: RE: Response cut off after 10 seconds when using NIO2 connector That's certainly not the case, I have no problem accessing 8443. Here is the connector config, only difference on the 8443 server is the protocol, address, and port. - Matt -Original Me

RE: Response cut off after 10 seconds when using NIO2 connector

2017-07-12 Thread Matt Cosentino
4:56 AM To: Tomcat Users List Subject: AW: Response cut off after 10 seconds when using NIO2 connector Hi Matt, > -Ursprüngliche Nachricht- > Von: Matt Cosentino [mailto:mcosent...@cacorp.com] > Gesendet: Dienstag, 11. Juli 2017 19:35 > An: Tomcat Users List > Betre

AW: Response cut off after 10 seconds when using NIO2 connector

2017-07-12 Thread Kreuser, Peter
Hi Matt, > -Ursprüngliche Nachricht- > Von: Matt Cosentino [mailto:mcosent...@cacorp.com] > Gesendet: Dienstag, 11. Juli 2017 19:35 > An: Tomcat Users List > Betreff: Response cut off after 10 seconds when using NIO2 connector > > I'm using Tomcat 8.5.16 w

Response cut off after 10 seconds when using NIO2 connector

2017-07-11 Thread Matt Cosentino
I'm using Tomcat 8.5.16 with the NIO2 connector and OpenSSL. It seems that if a request runs for more than 10 seconds, Tomcat simply cuts off the response. This does not happen with either the NIO or APR connectors. I'm using all default settings. Is this expected behavior or am I missing a sett