[
https://issues.apache.org/jira/browse/CAMEL-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397809#comment-13397809
]
Babak Vahdat commented on CAMEL-5310:
-------------------------------------
And I also think instead of the statements like:
{code}
LOG.debug("…", new Object[] {A, B, C});
{code}
We could better do:
{code}
if (LOG.isDebugEnabled()) {
LOG.debug("…", new Object[] {A, B, C});
}
{code}
which would avoid unnecessary object array instantiation in case the
Debug-Level is *not* enabled, making GC a bit happier :-)
> Add more logging when using SSLContextConfiguration
> ---------------------------------------------------
>
> Key: CAMEL-5310
> URL: https://issues.apache.org/jira/browse/CAMEL-5310
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: David Valeri
> Fix For: 2.11
>
>
> When using SSL it can be a bit pain to see what chipters, protocols,
> algorithms, and whatnot is available in the JVM. This can be different from
> SUN, Oracle, IBM, OpenJDK etc. Also between JDK versions as well.
> And if you have bouncycastle installed or not etc.
> We should add more logging details in the org.apache.camel.util.jsse classes
> so people can better see whats in use.
> Also it would be nice with some option to turn on the configuration, that
> logs a nice summary of all those details at INFO level. This makes it much
> easier to troubleshoot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
