Issue

• User set up fabric configuration and update it to the R2P6.
• But problem is RMI configuration changes are not persisted when made to org.apache.karaf.management.cfg.
• User trying to correct serviceUrl with following commands :

        JBossFuse:fuseadmin@child1> config:edit org.apache.karaf.management
        JBossFuse:fuseadmin@child1> propset serviceUrl service:jmx:rmi://myHostName:44447/jndi/rmi://myHostName1102/karaf-child1
        JBossFuse:fuseadmin@child1> prop
        propappend    propdel       proplist      propset
        JBossFuse:fuseadmin@child1> proplist
           rmiRegistryPort = 1102
           serviceUrl = service:jmx:rmi://myHostName:44447/jndi/rmi://myHostName:1102/karaf-child1
           jmxRealm = karaf
           objectName = connector:name=rmi
           threaded = true
           felix.fileinstall.filename = file:/apps/platform/jboss-fuse-6.1.0.redhat-379/instances/child1/etc/org.apache.karaf.management.cfg
           daemon = true
           service.pid = org.apache.karaf.management
           rmiServerPort = 44447
        JBossFuse:fuseadmin@child1> config:update
        JBossFuse:fuseadmin@child1> config:list | grep serviceUrl
           serviceUrl = service:jmx:rmi://myHostName:44447/jndi/rmi://myHostName:1102/karaf-child1
        JBossFuse:fuseadmin@child1>

• Everything works fine and serviceUrl persisted to the config file :

/apps/platform/jboss-fuse-6.1.0.redhat-379/instances/child1/etc/org.apache.karaf.management.cfg 

• After restart of the node the serviceUrl is wrong again:

  service:jmx:rmi://null:44447/jndi/rmi://null:1102/karaf-child1

• Strange that configuration changes are not persisted.
• After applying the patch (Rollup 2 Patch 6) on Fuse 6.1.0 ESB, the child containers were not recognised by the monitoring platform (Jboss Operations Network 3.3).
• We analysed the configuration and realized that the JMX serviceUrl in PID: org.apache.karaf.management is having a "null" value on host name. The workaround (for time-being) is to set this value manually to 0.0.0.0.
• After applying patch 6.1.1 R2P6 to Corporate Fuse ESB on Saturday 22nd August, the core functionality of the ESB was working as expected while the JMX monitoring configuration had an issue with child containers (all proxies, routes & amqs).
• The identified workaround/fix for this issue is to update this config everytime a child container is restarted. Is there any better way to resolve this issue ?
• For JVM resource monitoring we use Java visual VM. When we try to connect we are getting some error. Syntax of the JMX url

service:jmx:rmi://IP:44450/jndi/rmi://IP1105/karaf-childname