Problems starting Fuse ESB using the Java Service Wrapper

Solution Verified - Updated -

Issue

  • I am using the Java Service Wrapper to start Fuse ESB however, the container does not get started.
  • Where do I look to see why the Fuse ESB container does not start when using the Java Service Wrapper

To determine why the Fuse ESB container did not start when using the Java Service Wrapper you should have a look at the log created by the wrapper service. This log is created by default in [fuse_esb]/data/log/wrapper.log. This is also configurable in [fuse_esb]/etc/karaf-wrapper.conf by setting the following property:

# Log file to use for wrapper output logging.
wrapper.logfile=%KARAF_DATA%/log/wrapper.log

If you see something similar to the following in the wrapper.log it may indicate you have not set the java executable in your path:

STATUS | wrapper  | 2013/04/18 14:25:04 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2013/04/18 14:25:04 | Launching a JVM...
ERROR  | wrapper  | 2013/04/18 14:25:04 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2013/04/18 14:25:04 | JVM exited while loading the application.

Environment

  • Fuse ESB Enterprise 7.1
  • Jave Service Wrapper

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In