Follow the below steps to troubleshoot the error Make sure the service you're trying to connect to is actually running on the designated Host/IP and Port. Ensure the service is accessible by performing the below steps from the Applications Manager ...
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 ...
Solution: Check if the mongod / mongos instance is running in the host name specified. Check if the port number is given correctly. If mongod / mongos is running in authenticated mode, then enable "Is Authentication required" and give correct ...
1. Check Host and Port Accessibility Ensure that the Redis host and port are accessible from the server where Applications Manager is installed. Make sure there are no network restrictions or firewall rules blocking access to the Redis server. To ...
Solution: Check if the host name is correct. Check if the port number given is the JMX port number. We need JMX port number and not Cassandra DB port number for monitoring. The JMX port number will be available in cassandra-env.sh file. if cassandra ...