Specify SSL protocol for useSSL=true #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
January 14, 2022 14:54
|
Actually, this was sent to the wrong branch. I removed the merge from master and manually merged it to development. |
lmajano
pushed a commit
that referenced
this pull request
Nov 25, 2024
Add BoxLang support to Consumer.cfc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SSL-enabled connections would throw
SSLContext not available - java.security.NoSuchAlgorithmExceptionon the line:factory.useSSLProtocol( thisUseSSL );(
thisUseSSL===true)From glancing at the javadocs, it looks like it wanted the actual protocol to use there.
'TLSV1.2'worked when we tried it for our SSL-enabled RabbitMQ server, so I put that in as a default but allowed it to be overridden.Updated the README with that example and also adjusted the port to
5671which is the default AMQP SSL listener.