Return-Path: 
 <dev-return-40195-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8E53210E31
	for <apmail-activemq-dev-archive@www.apache.org>;
 Mon,  2 Sep 2013 23:58:53 +0000 (UTC)
Received: (qmail 90565 invoked by uid 500); 2 Sep 2013 23:58:52 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 90515 invoked by uid 500); 2 Sep 2013 23:58:52 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 90463 invoked by uid 99); 2 Sep 2013 23:58:52 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 23:58:52 +0000
Date: Mon, 2 Sep 2013 23:58:52 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12547179.1332242923385.69173.1378166332262@arcas>
In-Reply-To: <JIRA.12547179.1332242923385@arcas>
References: <JIRA.12547179.1332242923385@arcas>
Subject: [jira] [Resolved] (AMQ-3779) Allow logging broker plugin to use a
 log per destination
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Gary Tully resolved AMQ-3779.
-----------------------------

    Resolution: Fixed

implemented in http://git-wip-us.apache.org/repos/asf/activemq/commit/3222767e
                
> 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