You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org> on 2009/09/16 16:40:57 UTC

[jira] Resolved: (QPID-2016) Reload Log4J configuration file

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

Aidan Skinner resolved QPID-2016.
---------------------------------

    Resolution: Fixed

> Reload Log4J configuration file
> -------------------------------
>
>                 Key: QPID-2016
>                 URL: https://issues.apache.org/jira/browse/QPID-2016
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Management : JMX Console
>    Affects Versions: 0.6
>            Reporter: Aidan Skinner
>            Assignee: Aidan Skinner
>             Fix For: 0.6
>
>
> After changing the log4j configuration file through the management console it would be good to be able to force a reload of the file without having to have the watch interval configured. 

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