JON cannot manage JBoss servers after upgrading from EAP 4 to 5 with jmx-invoker domain

Solution Verified - Updated -

Issue

After adding EAP and SOA-P 5 instances to JON we cannot manage them, but can still manage the EAP 4 instances. Both SOA-P 4.3 and EAP/SOA-P 5 have a secured JMX-invoker based on the same user/password. We have LDAP for JMX-console but we are using another domain for JMX-Invoker.

Environment

  • JBoss Operation Network (JON) 3
  • JBoss Enterprise Application Platform (EAP) 5

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