-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 12/1/16 5:59 PM, Christopher Schultz wrote:
> All,
>
> I'm trying to use JMX to do things with Tomcat Connectors and
> ProtocolHandlers. Specifically, I'd like to re-load the keystore
> (really certificate) used for an HTTPs connection.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm trying to use JMX to do things with Tomcat Connectors and
ProtocolHandlers. Specifically, I'd like to re-load the keystore
(really certificate) used for an HTTPs connection.
I'm currently using Tomcat 8.0.30 for my testing.
It looks like
sslEnabledProtocols is now just protocols for one thing. And you have to
put your certificate stuff in an sub-section to the
connector now. Here's how ours had to be reconfigured (on 8443 instead
of 443) using NIO and JSSE:
protocol="org.apache.coyote.http11.Http11NioProtocol"
Thanks for your reply, unfortunately I know very little about Tomcat beyond the
server.xml config below.
What are "hooks" and or whats been deprecated related to the below, or is there
a new example config for using a .pfx Keystorefile?
-Original Message-
From: Jim Weill
Are you using the 8.5 reference?
https://tomcat.apache.org/tomcat-8.5-doc/config/http.html
When we updated to 8.5, we also found things changed with the connector
for SSL. The above page is the current guide, and you'll notice several
of the hooks have been deprecated since 6.0
jim
On
Thanks for replying, some more information.
Tomcat 8.0 works fine with this configuration (Ive tested both installs on same
server, same .pfx)
(note no other changes anywhere, just a fresh install and modifying the
server.xml)
We have been using this config since 6.0 through 8.0.
Something
Hi,
My application with ZK using dynamic Groovy Script to load ZK components.
Whole things is working fine with non-clustered environment.
Recently I have started testing my application with Clustered Environment.
I am testing with ZK 7.0.8 and Tomcat 8.5.8
In my groovy scripts FindPeople is a
SSL handshake in AsyncChannelWrapperSecure fails with the
"javax.net.ssl.SSLException: TODO" error.
Its failing because of BUFFER_OVERFLOW during handshake.
Caused by: javax.net.ssl.SSLException: TLS handshake returned an unexpected
status [BUFFER_OVERFLOW]
at
