Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <6075803.1200513524334.JavaMail.jira@brutus>
Date: Wed, 16 Jan 2008 11:58:44 -0800 (PST)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1361) Logging improvement contribution
In-Reply-To: <3589361.1187003762752.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/activemq/browse/AMQ-1361?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D41=
036#action_41036 ]=20

Hiram Chirino commented on AMQ-1361:
------------------------------------

The ip clearance document is now completed:

https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clea=
rance/activemq-logging-amq-1361.xml

Will bring in patch shortly.

> Logging improvement contribution
> --------------------------------
>
>                 Key: AMQ-1361
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1361
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker, Transport
>    Affects Versions: 5.0.0
>            Reporter: David Mart=EDn Clavo
>            Assignee: Hiram Chirino
>             Fix For: 5.1.0
>
>         Attachments: log_analyzer_tool.zip, new_patch_and_tool.zip, patch=
1.zip, patch2.zip
>
>
> Hello people,
> After our proposal some time ago (view http://www.nabble.com/Logging-impr=
ovement-proposal-tf3570794s2354.html#a9976200), we would like to add a litt=
le contribution to the ActiveMQ code, and we hope that the ActiveMQ develop=
ers and users like it.
> We thought it would be good to improve ActiveMQ logging's capabilities, i=
n order to make debugging, tracing, and understanding ActiveMQ easier.
> For this, we have added customization of ActiveMQ's Transport level loggi=
ng, allowing users to write their own logging formats. Also, we have added =
dynamic control of this logging functions (via JMX). We have also developed=
 a simple tool to analyze the log files produced.
> We have split the contribution into 2 patches, one to add customized log =
formats functionality, and the other to add dynamic management of logging v=
ia JMX. 1st patch is against SVN rev. 564978. 2nd patch is against 1st patc=
h (incremental).
> *A. New features*
> (1) Logging enhancements (1st patch):
> It is now possible to customize what will be written to the log file at t=
ransport level, by writing a custom class which implements the new LogWrite=
r interface.
> Also, the option: logWriterName =3D name has to be added to a transport U=
RI to choose which class (format) will be used (more details on how to impl=
ement your own class / format later).
> To activate transport logging, the trace=3Dtrue flag has to be used.
> People who don't want to use the new functionality will not have to chang=
e their URI's.
> (2) Dynamic control of logging enhancements (2nd patch):
> (a) Added ability to reload log4j.properties file to the BrokerView MBean=
.
> (b) If the option dynamicManagement=3Dtrue is appended to the URI, transp=
ort logging can be managed through JMX:
> =09-Logging can be switched on / off for every transport or for all of th=
em at once.
> =09-If the option startLogging=3Dfalse is appended to the URI, a transpor=
t will initially not log, but a TransportLogger instance will be created, a=
nd later it can be activated by JMX.
> =09-Another option lets the user change the JMX port used for these funct=
ions.
> (3) Log parsing and analysis tool:
> The tool parses log files (any number of them) of the CustomLogWriter for=
mat (our own implementation of the LogWriter interface) and has the followi=
ng features:
> (a) The tool detects incorrect situations at Transport level: sent but no=
t received messages, duplicate messages at transport level.
> (b) The tool can show the communication sequence for a message ("travel p=
ath" of a message).
> (c) Other features:
> =09(c1) Loading of log files is done by choosing a directory with them.
> =09(c2) Incorrect features can be filtered per type or per connection.
> =09(c3) Long, hard to read connection / client IDs can be replaced by sho=
rt, easy to compare IDs.
> =09(c4) Summary of connections, producers, consumers, log files.
> Some screen shots are included.
> (Continues on first comment)

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