I know this question may be asked several times, but my question is a little bit different.
I can start Weblogic server in Eclipse without error.
I tried to start in Eclipse Weblogic Server in debug mode to debug a LOCAL application (not remote debug), but I got the “Failed to connect to remote VM” error. To make sure the problem is from Eclipse, I started manually Weblogic with startWeblogic.cmd with debugFlag=true
in the bin\setDomainEnv.cmd, and then in Eclipse tried debugging Remote Java Application with the same debug port, the debug worked without error.
I also tried to compare the output of both launch method, they both contain the option for "Starting WLS with line": -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8022,server=y,suspend=n
. The only difference is that in Eclipse there's the java version, but no in Weblogic version.
I tried the solution in Eclipse Error: “Failed to connect to remote VM”, checking whether the debug port is occupied, and it is occupied by the same process java.
Another strange thing is that when I launch debug mode in Eclipse when the server is stopped, the error appears once. When I launch debug when in Eclipse when the server is started, the same error appears twice.
I'm using proxy in Eclipse, and I have to. But I was using the same configuration before when there was no such error.
Could you please help me with something I can check for the Weblogic Eclipse plugin? Thanks very much!
Just restart the Java application in debug mode. One of the human error which causes "Failed to connect to remote VM. Connection refused". Some time typo on hostname or port causes Eclipse trying to connect different servers or a different port, which is an obvious reason you get this error.
Select the Debug tab. Expand the scope labeled default or weblogic. Select the check box for the debug scopes or attributes you want to enable. Click Enable to enable (or Disable to disable) the debug scopes or attributes you have selected.
In your remote machine, try to disable the firewall and then try connecting it. If firewall is enabled this is a common error we get. Ex: service firewalld stop (or) systemctl stop firewalld
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With