[
https://issues.apache.org/jira/browse/QPID-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack resolved QPID-2042.
------------------------------------
Resolution: Fixed
Changes reviewed, look ok with use of random rather than tmp which was causing
filesystem issues on some platforms for the move. Probably would be good to add
some FAQ entries to the docs with the error/warn messages generated and what
the user could do it (for example) the access rights file back up cannot be
copied back to the original leaving them right-less.
> update to the management access rights may not be saved to disk, but still
> report success
> -----------------------------------------------------------------------------------------
>
> Key: QPID-2042
> URL: https://issues.apache.org/jira/browse/QPID-2042
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5
> Reporter: Robbie Gemmell
> Assignee: Martin Ritchie
> Priority: Critical
> Fix For: 0.6
>
>
> update to the management access rights may not be saved to disk, but still
> report success
> Certain use of the File.renameTo() function is not accompanied by a check of
> the boolean result, meaning a failed rename can leave the new file in the
> wrong location. As a result the existing file may not be replaced without
> indication of error, though the cached rights will have been updated, meaning
> the update would appear successful but simply be temporary. This has been
> observed in a situation where the OS Temp dir is on one (local) file system,
> and the broker configuration is on another (remote NFS) filesystem, which
> caused the rename to fail unnoticed.
--
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-subscr...@qpid.apache.org
