[
https://issues.apache.org/jira/browse/QPIDJMS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388640#comment-14388640
]
ASF subversion and git services commented on QPIDJMS-34:
--------------------------------------------------------
Commit 9db79b9544777dfd2df2935623a2fccc4184b12a in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=9db79b9 ]
QPIDJMS-34: reduce severity of logging about server mechanisms we dont support,
dont catch Errors
> a warning is logged when connecting for each unknown server SASL mechanism
> --------------------------------------------------------------------------
>
> Key: QPIDJMS-34
> URL: https://issues.apache.org/jira/browse/QPIDJMS-34
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.1.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.2.0
>
>
> When connecting to a server that supports SASL mechanisms the client does not
> support, a wrning is logged for each such mechanism, e.g:
> {noformat}
> 2015-03-31 15:29:53,073 [localhost:5672]] - WARN SaslMechanismFinder
> - Caught exception while searching for SASL mechanisms: Mechanism scheme
> NOT recognized: [GSS-SPNEGO]
> {noformat}
> As it is fairly likely this could occur and it does not really represent a
> problem as its partly why the mechanism list exists to allow negotiation, and
> an exception will be thrown to the application if no mechanisms match, this
> case should be treated separately form other cases and the logging for it
> reduced to debug to avoid unecessary alarm to users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
