Can .NET ActiveMQ clients discover Fabric managed A-MQ broker instances?

Solution Verified - Updated -

Environment

  • JBoss Fuse 6.1
  • JBoss Fuse 6.0
  • .NET ActiveMQ client

Issue

Can .NET ActiveMQ clients discover Fabric managed A-MQ broker instances from the Fabric runtime registry using the Fabric discovery protocol discovery:(fabric://<groupName>)?

Resolution

.NET clients of A-MQ do not support discovering broker instances from the Fabric runtime registry.
If you want to access those Fabric managed broker instances from .NET you will need to configure these instances to listen on a fixed port and then use a failover url such as failover:(tcp://brokerA:6161,tcp://brokerB:61616) in your .NET clients.
Java clients can continue to use Fabric discovery.

See article 1242263 on how to assign a fixed port to a Fabric managed broker instance.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

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