During kit testing for Fuse ESB (7.1.0.fuse-045) I noted the following that my children disappear after restart and also root status is not always correct.

1. start fuseesb
2. enter admin:list console

FuseESB:karaf@root> admin:list
SSH Port RMI Ports State Pid Name
[ 8101] [1099/44444 ] [Started ] [74113] root

3. Add two children - see attached addChildren script
4. Re-run admin:list

FuseESB:karaf@root> admin:list
SSH Port RMI Ports State Pid Name
[ 5602] [5502/5802 ] [Started ] [74236] hadoop
[ 5601] [5501/5801 ] [Started ] [74223] imgateway
[ 8101] [1099/44444 ] [Started ] [74113] root

5. Shutdown Fuse ESB and restart. Admin:list loses my hadoop child and shows root as stopped:

...
FuseESB:karaf@root> admin:list
SSH Port RMI Ports State Pid Name
[ 5601] [5501/5801 ] [Started ] [74223] imgateway
[ 8101] [1099/44444 ] [Stopped ] [ 0] root
FuseESB:karaf@root>
....

6. If I try to stop the hadoop instance use the stop script in the instance bin directory, I get an error:

wildflower:fuse-esb-7.1.0.fuse-045 sjavurek$ ./instances/hadoop/bin/stop
Error execution command 'stop': Instance 'hadoop' does not exist

However, I can connect to it and do stuff, i.e:

wildflower:fuse-esb-7.1.0.fuse-045 sjavurek$ ./bin/client -a 5602 -u admin -p admin list
START LEVEL 100 , List Threshold: -1
ID State Blueprint Level Name
[ 0] [Active ] [ ] [ 0] System Bundle (4.0.3.fuse-71-045)
[ 1] [Active ] [ ] [ 5] OPS4J Pax Url - mvn: (1.3.5)
.....