While trying to add JBoss monitor ( version 6 or below ), I get the message "Connection refused to host: 127.0.0.1;"
Reason:
JBoss binds to localhost by default. So applications manager cannot make a TCP connection to JBoss.
Solution:
In the terminal, add the parameter '-b 0.0.0.0' while starting the JBoss instance so that it binds to all the available IP addresses.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...While trying to monitor JBoss, I get the error 'Unable to collect Data for <host name>' while the JVM and EJB details are missing.
Reason 1: jbossagent.sar hasn't been deployed in the JBoss server Applications Manager collects JBoss MBean details by directly connecting to the JBoss JNDI Naming service. The application http-invoker.sar which comes by default with JBoss ...I'm not able to monitor the JBoss Application Server and I get an error message.
The below troubleshooting steps are for JBoss version 6 and below. Step 1: JBoss host and Applications Manager host are not accessible from each other. Applications Manager collects JBoss MBean details by directly connecting to the JBoss JNDI Naming ..."Failed Exception : Connection failure" while trying to add WebLogic monitor
Check whether the WebLogic host and port is accessible via TELNET. Check if you have used the configured listener address while trying to add the monitor. Listener can be obtained under Environment -> Servers -> <myserver> -> Configuration -> General ...How to get ISP data in Real User Monitor?
The default setting of the Real User Monitor does not display ISP data for the end user. To obtain ISP data, you have the option to use a third-party Geolocation API. Currently, RUM exclusively supports APIs that provide responses in JSON format. ...