Why starting JBoss Fuse as a service wrapper hangs for ever without internet access?
Issue
- While starting the JBoss Fuse as a service wrapper it hangs at the following logging:
From the logs it is hanging here:
11:04:27,791 | INFO | -610328-thread-1 | BlueprintExtender | 12 - org.apache.aries.blueprint.core - 1.0.1.redhat-610328 | No quiesce support is available, so blueprint components will not participate in quiesce operations
11:04:28,116 | INFO | -610328-thread-2 | BlueprintContainerImpl | 12 - org.apache.aries.blueprint.core - 1.0.1.redhat-610328 | Bundle org.apache.karaf.shell.console is waiting for dependencies [(objectClass=org.apache.felix.service.threadio.ThreadIO), (objectClass=org.apache.felix.service.threadio.ThreadIO), (objectClass=org.apache.felix.service.command.CommandProcessor)]
11:04:28,128 | INFO | -610328-thread-3 | BlueprintContainerImpl | 12 - org.apache.aries.blueprint.core - 1.0.1.redhat-610328 | Bundle org.apache.karaf.shell.console is waiting for dependencies [(objectClass=org.apache.felix.service.command.CommandProcessor)]
- If we try to start fuse with the initial
"$JBOSSFUSE_HOME/bin/start"
instead of the wrapper script the server starts ok. - The box where the fuse is being attempted to be started as a service is not connected to the internet.
Environment
- JBoss Fuse
- 6.1.0 Beta
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.