Fabric child containers are not getting started

Solution Verified - Updated -

Issue

  • Fabric child containers are not getting started
JBossA-MQ:admin@root_2> fabric:container-start -f xxx
The list of container names: [xxx]
Error executing command: Instance already started
  • logs :
2017-05-19 18:26:09,912 | ERROR | MCF-1-thread-1   | fabric-core                      | 82 - io.fabric8.fabric-core - 1.2.0.redhat-630187 | [io.fabric8.profile.urlhandler(33)] Failed creating the component instance; see log for reason
2017-05-19 18:26:09,913 | ERROR | lixDispatchQueue | fabric-configadmin               | 85 - io.fabric8.fabric-configadmin - 1.2.0.redhat-630187 | FrameworkEvent ERROR - io.fabric8.fabric-configadmin
java.lang.NoClassDefFoundError: x/y/introscope/agent/trace/IIntelligentInstrumentationMethodTracer
        at java.lang.Class.getDeclaredMethods0(Native Method)[:1.8.0_92]

Environment

  • Red Hat JBoss AMQ
    • 6.3.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
Close

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