JBoss Fuse doesn't fully start and log shows java.io.IOException: Failed to rename configuration file

Issue

• Fuse server does not start properly
• Fuse container does not start

The JBoss Fuse container fails to fully initialize, the process is running however the container commands are not available. In log the following error is seen:

08:37:53,335 | ERROR | FelixStartLevel  | fileinstall                      | 9 - org.apache.felix.fileinstall - 3.5.0 | Failed to install artifact: C:\MySoftwares\Fuse630\Test\jboss-fuse-6.3.0.redhat-187\etc\jmx.acl.org.apache.karaf.security.jmx.cfg
java.io.IOException: Failed to rename configuration file from 'C:Fuse630\jboss-fuse-6.3.0.redhat-187\data\cache\bundle7\data\config\jmx\acl\org\apache\karaf\security\jmx.config4975039803703133788.tmp' to 'C:\Fuse630\jboss-fuse-6.3.0.redhat-187\data\cache\bundle7\data\config\jmx\acl\org\apache\karaf\security\jmx.config
    at org.apache.felix.cm.file.FilePersistenceManager._store(FilePersistenceManager.java:717)[7:org.apache.felix.configadmin:1.8.4]
    at org.apache.felix.cm.file.FilePersistenceManager.store(FilePersistenceManager.java:654)[7:org.apache.felix.configadmin:1.8.4]
    at org.apache.felix.cm.impl.CachingPersistenceManagerProxy.store(CachingPersistenceManagerProxy.java:236)[7:org.apache.felix.configadmin:1.8.4]
    at org.apache.felix.cm.impl.ConfigurationImpl.update(ConfigurationImpl.java:381)[7:org.apache.felix.configadmin:1.8.4]
    at org.apache.felix.cm.impl.ConfigurationAdapter.update(ConfigurationAdapter.java:131)[7:org.apache.felix.configadmin:1.8.4]
    at org.apache.felix.fileinstall.internal.ConfigInstaller.setConfig(ConfigInstaller.java:249)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.ConfigInstaller.install(ConfigInstaller.java:76)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:241)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.FileInstall.updated(FileInstall.java:243)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.fileinstall.internal.FileInstall.start(FileInstall.java:120)[9:org.apache.felix.fileinstall:3.5.0]
    at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)[org.apache.felix.framework-4.4.1.jar:]
    at org.apache.felix.framework.Felix.activateBundle(Felix.java:2154)[org.apache.felix.framework-4.4.1.jar:]
    at org.apache.felix.framework.Felix.startBundle(Felix.java:2072)[org.apache.felix.framework-4.4.1.jar:]
    at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1299)[org.apache.felix.framework-4.4.1.jar:]
    at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)[org.apache.felix.framework-4.4.1.jar:]
    at java.lang.Thread.run(Thread.java:745)[:1.8.0_25]

The actual file may differ each the time container is started and container may fully start after several attempts. Note, this issue only occurs on a clean start of the container after the data directory has been deleted.