Problem Starting the FUSE ESB Runtime

[jsbournival]

Hi ppl,

I'm having a problem starting my local fuse esb 4.0.0.4 runtime:

After I installed it, everything went fine.  But after a reboot, I couldn't start it with the servicemix console invite.  Its throwing me a bunch of DEBUG statments, and then nothing.  Can you see something I do wrong?

$JAVA_HOME is set to 1.6

$SERVICEMIX_HOME=/opt/servers/fuse-esb/fuse-esb-4.0.0.4

Both of the latter are on the PATH

Also I'm on OS X

Thanks for your answers!

Here is the trace:

$ servicemix

servicemix: Ignoring predefined value for SERVICEMIX_HOME

DEBUG Scheduling task ManagedService Update: pid=org.ops4j.pax.url.mvn

DEBUG Running task ManagedService Update: pid=org.ops4j.pax.url.mvn

DEBUG Scheduling task ManagedService Update: pid=org.ops4j.pax.url.wrap

DEBUG Running task ManagedService Update: pid=org.ops4j.pax.url.wrap

DEBUG Scheduling task ManagedServiceFactory Update: factoryPid=org.apache.servicemix.kernel.filemonitor.FileMonitor

DEBUG Running task ManagedServiceFactory Update: factoryPid=org.apache.servicemix.kernel.filemonitor.FileMonitor

DEBUG Scheduling task Update: pid=org.apache.servicemix.features

DEBUG Running task Update: pid=org.apache.servicemix.features

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.apache.servicemix.features

DEBUG Running task Fire ConfigurationEvent: pid=org.apache.servicemix.features

DEBUG Scheduling task Update: pid=org.ops4j.pax.logging

DEBUG Scheduling task Update: pid=org.apache.servicemix.transaction

DEBUG Scheduling task Update: pid=org.ops4j.pax.url.mvn

DEBUG Scheduling task Update: pid=org.apache.servicemix.management

DEBUG Scheduling task Update: pid=org.apache.servicemix.shell

DEBUG Running task Update: pid=org.ops4j.pax.logging

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.ops4j.pax.logging

DEBUG Running task Update: pid=org.apache.servicemix.transaction

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.apache.servicemix.transaction

DEBUG Running task Update: pid=org.ops4j.pax.url.mvn

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.ops4j.pax.url.mvn

DEBUG Running task Update: pid=org.apache.servicemix.management

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.apache.servicemix.management

DEBUG Running task Update: pid=org.apache.servicemix.shell

DEBUG Scheduling task Fire ConfigurationEvent: pid=org.apache.servicemix.shell

DEBUG Running task Fire ConfigurationEvent: pid=org.ops4j.pax.logging

DEBUG Running task Fire ConfigurationEvent: pid=org.apache.servicemix.transaction

DEBUG Running task Fire ConfigurationEvent: pid=org.ops4j.pax.url.mvn

DEBUG Running task Fire ConfigurationEvent: pid=org.apache.servicemix.management

DEBUG Running task Fire ConfigurationEvent: pid=org.apache.servicemix.shell

DEBUG Scheduling task ManagedService Update: pid=org.ops4j.pax.logging

DEBUG Running task ManagedService Update: pid=org.ops4j.pax.logging

[ubhole]

Did you see this problem after deploying anything? If yes, then a test case would be of big help. Other option you can try is clean data folder from your installation and restarting FUSE ESB.

Ulhas

[jsbournival]

Yep it did the trick.  Thank you.

I wonder, there wasn't anything (at least in my understanding) that could have breaked the startup.  Maybe some bundle in my cache? 

Do you know of any logs I could have turned on/or just look at, that would have told me what the error was?  Pretty mysterious.

[ubhole]

Yes, you can find the logs in data/logs directory itself. you can collect more logging by tunning the logging configuration in etc/org.ops4j.pax.logging.cfg file.

Ulhas