[
https://issues.apache.org/jira/browse/AMQ-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897402#comment-16897402
]
ASF subversion and git services commented on AMQ-7094:
------------------------------------------------------
Commit 70b2a4318375a573bdbda61303f5cfc19d33ff7d in activemq's branch
refs/heads/activemq-5.15.x from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=70b2a43 ]
AMQ-7094 - track the objectName with an annotated mbean such that the jmx audit
log event can extract that target of an mbean operation, fix and test
(cherry picked from commit d2b0affedb38c5439bce2fb5a8e321bc5d0ec713)
> AuditLog should show the target of the operation and not just arguments
> -----------------------------------------------------------------------
>
> Key: AMQ-7094
> URL: https://issues.apache.org/jira/browse/AMQ-7094
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, JMX
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0, 5.15.10
>
>
> When we enable to audit log (http://activemq.apache.org/audit-logging.html),
> some of the operations don't have any arguments that identify the target (for
> example, purge(), resetStatistics()). The output of audit log doesn't show
> the queue name.
> {code}
> 2018-08-31 11:19:43,803 | INFO | (6)-127.0.0.1 | audit |
> vemq.broker.util.DefaultAuditLog 27 | anonymous called
> org.apache.activemq.broker.jmx.QueueView.purge[] at 31-08-2018 11:19:43,801
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
