You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/08/16 22:45:14 UTC
[jira] Updated: (QPID-2016) Reload Log4J configuration file
[ https://issues.apache.org/jira/browse/QPID-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2016:
---------------------------------
Status: Ready To Review (was: In Progress)
> 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: Robbie Gemmell
> 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