activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2224) Enable Tracing of Messages in a network of brokers
Date Fri, 24 Apr 2009 13:22:38 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac resolved AMQ-2224.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Dejan Bosanac

Committed (a bit changed) in SVN revision 768300. Thanks. I also added the <traceBrokerPathPlugin/>
tag for easier configuration. Now we only need a wiki page to document all these plugins :)

> Enable Tracing of Messages in a network of brokers
> --------------------------------------------------
>
>                 Key: AMQ-2224
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2224
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.2.0
>         Environment: All
>            Reporter: Andreas Gies
>            Assignee: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.3.0
>
>         Attachments: amq-2224.txt
>
>
> In environments that have a larger network of brokers set up, it is sometimes of interest
which path a message has taken from the producer to the consumer. One could enable tracing
in the brokers and kind of review the log files, but this is very time consuming if not impossible.
I propose a small BrokerPlugin that can be used to append the brokerName to a given message
property. On the consumer side or in the logs we could then evaluate that property and see
exactly which broker has been touched by the message. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message