[
https://issues.apache.org/jira/browse/AMQ-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-3779:
----------------------------
Fix Version/s: 5.9.0
@Bhanu - maybe attempt a patch, we love contributions :-) In any event will try
to get to it for the next release.
> Allow logging broker plugin to use a log per destination
> --------------------------------------------------------
>
> Key: AMQ-3779
> URL: https://issues.apache.org/jira/browse/AMQ-3779
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Priority: Minor
> Labels: logging, plugin
> Fix For: 5.9.0
>
>
> Re:
> http://activemq.2283324.n4.nabble.com/How-to-log-all-incoming-msgs-of-Queue-quot-hello-quot-into-a-separate-logfile-td4487917.html
> Would be nice to configure the
> http://activemq.apache.org/logging-interceptor.html to use a send message log
> per destination so that destination messages can be easily partitioned.
> A logPerDestination boolean attribute, that would cause the plugin to use a
> logger of the form:
> org.apache.activemq.broker.util.LoggingBrokerPlugin.<destination name> for
> producer send events
> --
> Query on composites?
> For the simplest implementation, composites, they would have their unique log
> rather than parsing the composite and repeating the log message per
> destination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
