https://bz.apache.org/bugzilla/show_bug.cgi?id=63223
TehKantz <u...@kantzuker.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |REOPENED
--- Comment #2 from TehKantz <u...@kantzuker.com> ---
This is is the configuration used for the ssl connection as part of the tomcat
server.xml template:
<Connector port="8443"
protocol="org.apache.coyote.http11.Http11AprProtocol"
maxThreads="150" SSLEnabled="true" >
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
<SSLHostConfig>
<Certificate certificateKeyFile="conf/privkey.pem"
certificateFile="conf/cert.pem"
certificateChainFile="conf/chain.pem"
type="RSA" />
</SSLHostConfig>
</Connector>
I am not sure that the behavior is correct.
when it happens, the server gets into a blocking state rejecting requests from
all users across all WebApps, and the only way to stop it is killing the
process.
It Doesn't seems to be a desired behaviour, on top of that the logs created
from this are insane it blocks the IO of the server make it even harder to
shutdown the process
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
