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 ...REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...