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/17 17:09:14 UTC
[jira] Created: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
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
[jira] Updated: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Updated: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Assigned: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-2055:
------------------------------------
Assignee: Aidan Skinner (was: Robbie Gemmell)
Hi Aidan, can you review this change please, thanks.
> 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: Aidan Skinner
> 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
[jira] Resolved: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack resolved QPID-2055.
------------------------------------
Resolution: Fixed
Reviewed changes, looks ok though would possibly use setLinkedException when passing on exceptions/rethrowing.
> 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: Martin Ritchie
> 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
[jira] Reopened: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reopened QPID-2055:
----------------------------------
Assignee: Robbie Gemmell (was: Aidan Skinner)
> 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
[jira] Resolved: (QPID-2055) failed rename may leave the broker
without a log4j configuration when manipulating its contents with the
LoggingManagement MBean
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-2055.
---------------------------------
Resolution: Fixed
> 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: Aidan Skinner
> 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