Server and socket binding groups are exposed for unrelated domain resources when adding new managed server using JBoss EAP 6 managed plug-in for JBoss ON

Solution Unverified - Updated -


  • Mixes domain controller configuration in wizards
  • The domain configuration is mixed up in the create managed server wizard
  • I am able to select the host of domain controller 1, a server-group of domain 2 and the socket-binding-group of domain 3.
  • Only the possible values of my selected domain should be showed in the wizard.
  • I am not able to distinguish between the different test environments
  • Server groups from one domain show up as available for another domain
  • Socket binding groups from one domain show up as available for another domain


  • JBoss Operations Network (ON) 3.1.1, 3.1.2
  • JBoss Enterprise Application Platform (EAP) 6
  • JBoss Application Server (AS) 7 plug-in for JBoss ON
  • Two or more JBoss EAP servers running in domain mode and in inventory under the same platform
    • Each EAP domain defines one or more server groups or socket binding groups with a unique name:
      • Server 1: server-group name="main-server-group-01" profile="full", socket-binding-group name="full-sockets-01" default-interface="public"
      • Server 2: server-group name="main-server-group-02" profile="full", socket-binding-group name="full-sockets-02" default-interface="public"
  • Creating a new managed server in one of the EAP domains from the domain controller's child resources page

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