Major Description
If I cause a change to made to the broker configuration (say, adding a port) or the configuration of a virtualhost backed by a json file (say adding a queue), the Broker rewrites the underlying file(JsonFileConfigStore). However, in doing so, the file's original file permissions may be lost. In a POSIX based system, get the default permissions specified by the umask.
The user can workaround the issue by setting as suitably restrictive umask, but this will currently apply to all files created by Broker, even log files which a user may wish to carry a different permission, for operate reasons.
The Java Broker should strive to maintain permissions on such file by attempting to replacement file with the same permission set/attribute view as the old.