Fuse container sometimes does not start at boot time, after a disorderly shutdown, because its stored process ID is in use by a different process

Solution Verified - Updated -

Issue

When Fuse is shut down cleanly, it will set the process ID (PID) to zero in ìnstances/instance.properties. When Fuse restarts, it checks the stored PID and, if there already is a process with that ID, it refuses to start. This is to protect Fuse from running multiple instances accidentally.

Sometimes, purely by coincidence, another process other than Fuse will have started between the disorderly shutdown and restart of Fuse, and have the same PID as the stored Fuse PID. Although it is safe for Fuse to start in this situation, it has no way of knowing that.

Environment

  • Red Hat JBoss Fuse
    • All versions up to and including 6.3

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.