You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Martin Lichtin (JIRA)" <ji...@apache.org> on 2017/02/01 13:51:51 UTC
[jira] [Commented] (AMQ-6588) TransportConnection to show client-id
when reporting SecurityException
[ https://issues.apache.org/jira/browse/AMQ-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848389#comment-15848389 ]
Martin Lichtin commented on AMQ-6588:
-------------------------------------
E.g.
{noformat}
LOG.warn("Failed to add Connection id={}, clientId={} due to {}", info.getConnectionId(), clientId, e);
{noformat}
> TransportConnection to show client-id when reporting SecurityException
> ----------------------------------------------------------------------
>
> Key: AMQ-6588
> URL: https://issues.apache.org/jira/browse/AMQ-6588
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Martin Lichtin
> Priority: Trivial
>
> Please can we add the "clientId" to the WARNing log when reporting a SecurityException such as:
> {noformat}
> 2017-02-01 14:40:53,097 | WARN | ActiveMQ NIO Worker 3 | TransportConnection | ivemq.broker.TransportConnection 855 | 98 - org.apache.activemq.activemq-osgi - 5.14.0 | Failed to add Connection ID:myhost-50222-1485251692449-0:5 due to java.lang.SecurityException: User name [null] or password is invalid.
> {noformat}
> It would really help to find out where the erroneous connection is coming from.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)