"Failed Exception : Connection failure" while trying to add WebLogic monitor

"Failed Exception : Connection failure" while trying to add WebLogic monitor


  1. Check whether the WebLogic host and port is accessible via TELNET.
  2. Check if you have used the configured listener address while trying to add the monitor.
    1. Listener can be obtained under Environment -> Servers -> <myserver> -> Configuration -> General -> Listen Address field
  3. Check whether there is any firewall between WebLogic Host and the Applications Manager machine. If this is the case, then open WebLogic host and port in the Applications Manager side.
  4. Check whether Filters are enabled in Weblogic domain, and Applications Manager Host/IP is restricted.
    1. <mydomain> -> Security -> Filter
  5. Check whether the Hostname / IP address of WebLogic machine is resolvable from Applications Manager machine. The Hostname / IP address can be resolved by executing the nslookup command.
  6. Check whether the /etc/resolv.conf file (in windows it is Windows\System 32\drivers\etc\hosts file) in the Applications Manager Machine has correct domain.
  7. Enable T3 Tunneling by following the steps mentioned here.
  8. The jars might either be corrupted or outdated.  
  For version 12 and above, some WebLogic servers requires fullclient jars. Please use the jars below:
  1. Version 10       
  2. Version 12 & above
           

If the issue still exists, reach out to our support with the screenshot of the error obtained to appmanager-support@manageengine.com along with the latest Support Information File (SIF) from Applications Manager with print all logs enabled for analysis.

                  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 the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                    • 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 ...
                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...
                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...
                    • "Authentication Failed or Access denied" message is shown, when trying to add the Server Monitor through WMI mode.

                      Domain and IP Address Issues If the machine is part of a domain, specify the username in DOMAIN\Username format. For example: CORP\Administrator where CORP is the domain name and Administrator is the username. If the machine is not part of a domain, ...