-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging use of alpn-boot vs. tcnative jar. #508
Conversation
if (OpenSsl.isAvailable()) { | ||
LOG.info("gRPC is using the OpenSSL provider (tcnactive jar)"); | ||
} else { | ||
LOG.info("gRPC is using the JDK provder (alpn-boot jar)"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"JDK provider"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Thanks.
sslBuilder = createGrpcSslBuilder(); | ||
sslBuilder = GrpcSslContexts.forClient().ciphers(null); | ||
if (OpenSsl.isAvailable()) { | ||
LOG.info("gRPC is using the OpenSSL provider (tcnactive jar)"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to log this multiple times? If not, we can log in performWarmup().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I am fine with it. Per connection is OK.
LGTM |
Logging use of alpn-boot vs. tcnative jar.
There are a few issues related to using the tcnative jar. This one is about logging the use of tcnative or alpn-boot.