Changed startup behaviour with broken services in EAP 6.4 vs 6.1 / Fuse 6.2.1 vs. FSW 6.0.0

Solution In Progress - Updated -

Issue

We are migrating from FSW 6.0.0 to Fuse 6.2.1 on EAP 6.4, and noticed a what seems to be a change in the server's startup behaviour: If you have a deployment with several services, and one of them cannot be started for whatever reason, all other services are being stopped. In the previous version, the broken service was not started, but all other services continued to run.

Environment

  • Red Hat JBoss Fuse Service Works (FSW)
    • 6.0.0
  • Red Hat JBoss Fuse
    • 6.2.1
  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.1.1
    • 6.4.x

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