HA-JNDI discovery returns wrong reference in multiple JBoss EAP clusters environment

Solution Unverified - Updated -

Issue

We have multiple clusters within same network and each cluster has unique multicast address. We observed an odd behavior when trying to perform  HA-JNDI discovery from within one cluster to the another cluster, by  specifying jnp.discoveryGroup of the target remote cluster. It  unexpectedly returns its own local cluster HA-JNDI.

Environment

  • JBoss Enterprise Application Platform (EAP) 5.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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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