ActiveMQ slave broker failed to start due to javax.management.InstanceAlreadyExistsException after mq-fabric bundle refresh failure

Solution Verified - Updated -

Issue

  • ActiveMQ slave broker failed to start due to javax.management.InstanceAlreadyExistsException after mq-fabric bundle refresh failure

Environment

  • Red Hat Fuse (Fuse)
    • 6.3
  • Fuse Fabric (Fabric)
  • Microsoft Windows Server 2016
  • Microsoft SQL Server
  • ActiveMQ broker master/slave cluster through JDBC persistent adapter

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content