Child Container created as service does not start
Issue
-
We are facing issue when starting fuse child containers running as active passive with JDBC lock.
-
The active container is running on the other server. However, the passive container does not start at all. Even if we stopped the active container and started the passive one, it failed to start.
FuseESB:admin@esb-root-node02> container-list | grep esb-eq
esb-application-node01 1.2 true fabric, default, esb-application success
esb-application-node02 1.2 false fabric, default, esb-application success
- Tried to start the container from console but got the following error:
FuseESB:admin@esb-root-node02> container-start esb-application-node02
Error executing command: java.lang.IllegalArgumentException: Instance 'esb-application-node02' does not exist
FuseESB:admin@esb-root-node02> exit
Connection to localhost closed.
- Checked if the process was running but it turned out to be negative:
fuse@prodserver1:~$ps -efa | grep esb-application
fuse 24316 24218 0 20:01 pts/2 00:00:00 grep --color=auto esb-application
- Tried to start through service script:
fuse@prodserver1:~$/etc/init.d/esb-application-node02-service start
Starting esb-application-node02...
- But it did not start up. The Fuse logs showed that it was stopped a couple of days ago but never got started:
fuse@prodserver1:~$tail -f /opt/FuseESBEnterprise-7.1.0/instances/esb-application-node02/data/log/karaf.log
2013-09-03 16:01:04,243 | INFO | ispatcher thread | AbstractZKClient | ctZKClient$StateChangeDispatcher 361 | 59 - org.fusesource.fabric.fabric-zookeeper - 7.1.0.fuse-047 | StateChangeDispatcher terminated.
2013-09-03 16:01:04,250 | INFO | ad-1-EventThread | ClientCnxn | zookeeper.ClientCnxn$EventThread 511 | 58 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.1.0.fuse-047 | EventThread shut down
2013-09-03 16:01:04,250 | INFO | FelixStartLevel | ZooKeeper | org.apache.zookeeper.ZooKeeper 679 | 58 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.1.0.fuse-047 | Session: 0x240a41cdec40000 closed
2013-09-03 16:01:04,454 | INFO | FelixStartLevel | core | ? ? | 38 - org.apache.aries.jmx.core - 1.0.1.fuse-71-047 | Stopping JMX OSGi agent
2013-09-03 16:01:04,502 | INFO | FelixStartLevel | core | ? ? | 38 - org.apache.aries.jmx.core - 1.0.1.fuse-71-047 | Unregistering MBean with ObjectName [osgi.compendium:service=cm,version=1.3] for service with service.id [11]
2013-09-03 16:01:04,783 | INFO | FelixStartLevel | Activator | j.pax.logging.internal.Activator 59 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Disabling SLF4J API support.
2013-09-03 16:01:04,783 | INFO | FelixStartLevel | Activator | j.pax.logging.internal.Activator 62 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Disabling Jakarta Commons Logging API support.
2013-09-03 16:01:04,784 | INFO | FelixStartLevel | Activator | j.pax.logging.internal.Activator 65 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Disabling Log4J API support.
2013-09-03 16:01:04,784 | INFO | FelixStartLevel | Activator | j.pax.logging.internal.Activator 68 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Disabling Avalon Logger API support.
2013-09-03 16:01:04,785 | INFO | FelixStartLevel | Activator | j.pax.logging.internal.Activator 71 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Disabling JULI Logger API support.
Environment
- Fuse ESB
- 7.x
- Red Hat JBoss Fuse
- 6.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.