The JSON config file is not saved after startup until promted by additional change, which can result in unecessary generation of new IDs for objects on each startup.
For example, upon the first startup the initia-config within the broker jar is written out to disk and then loaded. This prompts generation of IDs for the objects in the configuration, but does not cause the file to be saved. If the broker is simply restarted the same generation of IDs occurs.
Similarly, if a user edited the config file and added a new object but did not specify an ID, one would be generated at each restart until they edited the config with the broker running and prompted it to save the current ID for the object.
The config store file should be immediately saved if any Ids are generated during startup.