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/10/20 18:13:59 UTC

[jira] Updated: (QPID-2055) failed rename may leave the broker without a log4j configuration when manipulating its contents with the LoggingManagement MBean

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

Robbie Gemmell updated QPID-2055:
---------------------------------

    Status: Ready To Review  (was: In Progress)

> failed rename may leave the broker without a log4j configuration when manipulating its contents with the LoggingManagement MBean
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2055
>                 URL: https://issues.apache.org/jira/browse/QPID-2055
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.5
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Critical
>             Fix For: 0.6
>
>
> Similar to QPID-2040,QPID-2041,QPID-2042, the LoggingManagement MBean makes use of File.renameTo to update the contents of the log4j XML configuration file on disk, and this is susceptible to failure when renaming across filesystems.

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