RE: OT: java.net.socket exception

Thanks Chris. Yes, I misspelled it, I said I'm not a developer. LOL I'm just trying to figure out WHY that setting would blow up a spring coded outbound connection like that. Thanks, Dream * Excel * Explore * Inspire Jon McAlexander Senior Infrastructure Engineer Asst. Vice President He/His

Re: OT: java.net.socket exception

Mark, Jon, On 5/26/23 04:39, Mark Thomas wrote: On 25/05/2023 20:46, jonmcalexan...@wellsfargo.com.INVALID wrote: So, to start I'm not a developer. With that said, have a development team that is getting the exception below in their Tomcat 9.0.74 implementation using Java 11 (also with Java

Re: Disabling hostname verification on websockets in Tomcat 8+

Ah, that's it! I was using the TrustEverythingTrustManager we had around from the rabbitmq client library, which just implements X509TrustManager, and I didn't realize that was

Re: Disabling hostname verification on websockets in Tomcat 8+

On 25/05/2023 22:52, V User wrote: The how-to on websockets ( https://tomcat.apache.org/tomcat-9.0-doc/web-socket-howto.html) says that you can bypass hostname verification with a custom TrustManager: "For secure server endpoints, host name verification is enabled by default. To bypass this

Re: OT: java.net.socket exception

On 25/05/2023 20:46, jonmcalexan...@wellsfargo.com.INVALID wrote: So, to start I'm not a developer. With that said, have a development team that is getting the exception below in their Tomcat 9.0.74 implementation using Java 11 (also with Java 8). After much troubleshooting with their