Using Fuse 6.2 in active/passive mode causes an accumulation of open listening ports

Solution Verified - Updated -

Issue

When Fuse is used in a active/passive mode of operation -- that is, multiple stand-alone (not Fabric8) instances of Fuse competing for a start-up lock -- the passive instance will continue to open listening ports until it becomes active. Over a long period of time the passive process could fail owing to a lack of available file descriptors.

Please note that the problem does not arise with master/slave operation controlled by Zookeeper in Fabric8, or when using a master/slave arrangement of A-MQ message brokers controlled by file or database locking -- it is associated only with active/passive locking in Fuse (more specifically Karaf) itself.

Environment

  • Red Hat JBoss Fuse
    • 6.2.0 GA
    • 6.2.0 P1, P2, and P3

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.