You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/05/22 02:40:17 UTC
[jira] [Commented] (AMQ-5771) In the logs add remote IP address in
case of authentication failure
[ https://issues.apache.org/jira/browse/AMQ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555367#comment-14555367 ]
ASF GitHub Bot commented on AMQ-5771:
-------------------------------------
GitHub user cshannon opened a pull request:
https://github.com/apache/activemq/pull/103
https://issues.apache.org/jira/browse/AMQ-5771
Including remote ip address when logging authentication failures
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cshannon/activemq AMQ-5771
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/103.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #103
----
commit 473fc0ea18d1ed24856c2dcc6d171892379d2a13
Author: Christopher L. Shannon <ch...@gmail.com>
Date: 2015-05-22T00:36:41Z
https://issues.apache.org/jira/browse/AMQ-5771
Including remote ip address when logging authentication failures
----
> In the logs add remote IP address in case of authentication failure
> --------------------------------------------------------------------
>
> Key: AMQ-5771
> URL: https://issues.apache.org/jira/browse/AMQ-5771
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.9.0
> Environment: All
> Reporter: JaySenSharma
>
> - In case of authentication failure, ActiveMQ currently logs something like:
> {code}
> 2015-02-27 13:56:59,740 [ActiveMQ NIO Worker 7126] WARN Service - Security Error occurred: User name [_________] or password is invalid.
> {code}
> - In order to find the culprit client, it would be very useful to add the remote IP address (and port) used while authenticating.
> - Currently we see that the timeout warnings do log such information:
> {code}
> [InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@4182d5fc[State = -1, empty queue]] WARN Transport - Transport Connection to: tcp://130.120.110.33:39338 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>3600000) long: tcp://130.120.110.33:39338
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)