Troubling Shooting - Configuring APM Jboss agent JMX MBean server connections Jboss domain environment

Body

Issue: The current KC only has instructions for enabling the JMX MBean server connections for a Jboss standalone environment.

https://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/jboss_config_agent_prereq_enable_server_connections.htm

The steps below provide the steps to enable the JMX MBean server connections in a Jboss domain environment

 

--RM-- Resource Monitoring for JBoss domain configuration. --RM--

 

1. One agent instance will be necessary for each JBoss server instance you monitor on each JBoss host.

Example: If you have a main-server-group with master and slave servers, you need to monitor both the

master and slave servers with separate agent instances.

They do not share all mbeans.

Note that if you run an application on the controller or a slave, they don't report average response time.

 

2. Create a JBoss user account with ApplicationRealm priviledges in each domain configuration directory for each JBoss server you monitor. This will be the user you will use in your JBoss agent configuration.

 

Example: <JBOSS_HOME>\bin\add-user.bat [-dc <JBOSS_HOME>\MyCustomHostDirectory\domain\configuration\]

 

Test: Observe that the user name is set in <JBOSS_HOME>\MyCustomHostDirectory\domain\configuration\application-users.properties

 

3. Ensure the JBoss user account from step 2. has a role with sufficient administrative authority.

 

Example: Re-run the JBoss add-user script for your monitoring user and give it ManagementRealm privileges with the SuperUser role.

 

4. Update the domain.xml for each JBoss host to set use-management-endpoint to false.

 

     <subsystem xmlns="urn:jboss:domain:jmx:1.3">

       <expose-resolved-model/>

       <expose-expression-model/>

     </subsystem>

  to

     <subsystem xmlns="urn:jboss:domain:jmx:1.3">

       <expose-resolved-model/>

       <expose-expression-model/>

       <remoting-connector use-management-endpoint="false"/>

     </subsystem>

  under all socket profiles for the servers you want to monitor on that server.

 

5. Update the hosts.xml file on each JBoss host to set its IP address.

  <interfaces>

   <interface name="management">

     <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

   </interface>

   <interface name="public">

    <inet-address value="${jboss.bind.address:127.0.0.1}"/>

   </interface>

 to

  <interfaces>

   <interface name="management">

     <inet-address value="${http://<your address>domain=jboss.bind.address.management<ServerIP accessable by agent>}"/>

   </interface>

   <interface name="public">

    <inet-address value="${jboss.bind.address:<ServerIP accessable by agent>}"/>

   </interface>

 

6. For each agent instance, make sure the JMX URI uses the proper port.

EAP 6: service:jmx:remoting-jmx://<ServerIP>:<Remoting port + offset binding for server instance>

EAP 7: service:jmx:remote+http://<ServerIP>:<Remoting port + offset binding for server instance>

 

Example: JMX URIs for a JBoss EAP 7 host named jboss-eap7-slave1 with 2 servers.

The first server uses the default http port 8080, and the second server has a port offset of 150.

service:jmx:remote+http://jboss-eap7-slave1:8080

service:jmx:remote+http://jboss-eap7-slave1:8230

 

To confirm the http port for each JBoss server, look in the "server.log" for each JBoss server after it has been started at least once.

For example, for a JBoss host named host1_server1, with a JBoss home of C:/EAP-7.0.0, the server.logs might be found at

C:/EAP-7.0.0/domain/servers/host1_server1/log/server.log.

 

Search for "server.log" from your JBoss home directory and determine the correct location for each server.log for the JBoss servers you monitor.

 

Example server.log message:

2018-10-23 09:08:19,875 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on http://protect-us.mimecast.com/s/7QQUCo2moxtrxXYfz626R?domain=10.33.100.86

 

--RM-- End Draft Instructions for JBoss domain configuration. --RM--

 

 

Subscribe and follow us for all the latest information direc tly on your social feeds:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

 

 

 

 

 

 

Check out all our other posts and updates:
Academy Blogs:	https://goo.gl/U7cYYY
Academy Videos:	https://goo.gl/T LfMoF
Academy Google+:	https://goo.gl/HnTs0w
Academy Twitter :	https://goo.gl/AhR8CL

 

 

 

 

 

 

 

< a href="https://www.ibm.com/developerworks/community/blogs/0587adbc - 8477 - 431f - 8c68 - 9226adea11ed?lang=en" style="width: 1159.61px; display: inline - block;" target="_blank">