[
https://issues.apache.org/activemq/browse/AMQ-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gies updated AMQ-2168:
------------------------------
Attachment: AMQ2168.txt
The attached file is a patch appliable to activemq-trunk. It replaces the
LogginBrokerPlugin with an enhanced implementation. The idea is to log all
events but be able to turn off logging for certain event groups by
configuration.
Currently the following groups are supported:
All : Log all Events
MessageEvents : Events related with producing, consuming and dispatching
messages
ConnectionEvents : Events related to connections and sessions
TransactionEvents : Events related to transaction handling
ConsumerEvents : Events related to consuming messages
ProducerEvents : Events related to producing messages
InternalEvents : Events normally not of Interest for users like failover,
querying internal objects etc
Everything is turned on by default.
> Improve LoggingBrokerPlugin
> ---------------------------
>
> Key: AMQ-2168
> URL: https://issues.apache.org/activemq/browse/AMQ-2168
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.2.0
> Environment: all
> Reporter: Andreas Gies
> Priority: Minor
> Attachments: AMQ2168.txt
>
>
> I was recently involved into analyzing the behavior of the ActiveMQ broker in
> different scenarios and was thinking that a Logging Plugin would be handy to
> have. The existing org.apache.activemq.broker.util.LoggingBrokerPlugin simply
> traces the send of messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
