[ https://issues.apache.org/jira/browse/AMQ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555370#comment-14555370 ]
Christopher L. Shannon commented on AMQ-5771: --------------------------------------------- This would be useful to me as well so I pushed up a pull request. > 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)