Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <497227906.1240482091645.JavaMail.jira@brutus>
Date: Thu, 23 Apr 2009 03:21:31 -0700 (PDT)
From: "Andreas Gies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2224) Enable Tracing of Messages in a network
 of brokers
In-Reply-To: <1164503783.1240481973051.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Andreas Gies updated AMQ-2224:
------------------------------

    Attachment: amq-2224.txt

This file contains a small plugin TraceBrokerPathPlugin that implements the suggested behavior.

> 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
>         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.