Error in log file while creating remote container

[ashish.mohan_ashish.mohan]

I see below error in log file while creating remote container even though the remote container is created successfully. Command that I use to create remote container is.

FMC:karaf@FuseManagementConsole> container-create-ssh --host  --profile myprofile TestRemoteContainer

The following containers have been created successfully:

        Container: TestRemoteContainer.

Errorin log file:

-

---

2013-02-22 20:19:59,239 | WARN  | p1070889758-9404 | ContainerImpl                    | ce.fabric.internal.ContainerImpl  532 | 54 - org.fusesource.fabric.fabric-core - 7.1.0.fuse-047 | Error while retrieving jmx domains. This exception will be ignored.

org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /fabric/registry/containers/domains/TestRemoteContainer

        at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)[49:org.fusesource.fabric.fabric-linkedin-zookeeper:7.1.0.fuse-047]

        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)[49:org.fusesource.fabric.fabric-linkedin-zookeeper:7.1.0.fuse-047]

        at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1448)[49:org.fusesource.fabric.fabric-linkedin-zookeeper:7.1.0.fuse-047]

        at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1476)[49:org.fusesource.fabric.fabric-linkedin-zookeeper:7.1.0.fuse-047]

-

---

This error is being logged so frequently that it fills the 10MB log file almost every minute.

[stlewis]

Yeah, this is due to the polling that FMC performs if you have the window open while creating a container.  We should probably avoid logging that message really since it's being ignored anyway.  I've gone ahead and created this issue so it doesn't get lost.

[ashish.mohan_ashish.mohan]

I realized that remote container was not able to start because it was looking for JAVA_HOME at //java/jdk1.7.0_09

once I copied jdk to this location, I was able to start the container and error is gone now.

I am not sure why karaf is looking for jdk at this location and why not at the JAVA_HOME already defined in .profile.