qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Gemmell (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Assigned: (QPID-1648) Enable live reconfiguration of Log4J settings for the Java broker via JMX
Date Mon, 16 Mar 2009 01:46:50 GMT

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

Robert Gemmell reassigned QPID-1648:
------------------------------------

    Assignee: Martin Ritchie  (was: Robert Gemmell)

Hi Martin, Aidan already committed this patch for me previously but could you review it please,
thanks.

> Enable live reconfiguration of Log4J settings for the Java broker via JMX
> -------------------------------------------------------------------------
>
>                 Key: QPID-1648
>                 URL: https://issues.apache.org/jira/browse/QPID-1648
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker, Java Management : JMX Console
>            Reporter: Robert Gemmell
>            Assignee: Martin Ritchie
>             Fix For: Eclipse MC M5
>
>         Attachments: log4j_config_changes.patch, QPID-1648_24feb2009.patch
>
>
> It would be useful to be able to update the Log4J settings for a running Java broker
via JMX, incase it was desirable to adjust logging to investigate an issue which became apparent
after startup. 
> Whilst Log4J supports monitoring its own configuration file for updates, the broker must
be started with this enabled for it to be of any use, and updating the settings by manually
modifying the xml file runs the risk of accidentally rendering the file invalid, which could
lead to serious issues when the update is detected and applied by Log4j.
> In order to address these issues, adding the ability to to update the settings via JMX
would allow users to be able to adjust the Log4J settings in 2 ways: by modifying the xml
file programatically rather than by hand, or by modifying the Log4J runtime settings directly,
allowing (temporary) updates even where Log4J has not been instructed to monitor its configuration
file for change.

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message