Keywords: Eclipse Remote Debugging | Connection Refused | Java Debug Configuration
Abstract: This paper provides an in-depth technical analysis of the 'Failed to connect to remote VM. Connection refused' error during Eclipse remote debugging sessions. Focusing on server configuration, port settings, and JVM debugging parameters, the article offers complete solutions with detailed step-by-step instructions and code examples. Covering major servers including Tomcat and GlassFish, it addresses specific configuration requirements for Windows service environments, ensuring comprehensive understanding of remote debugging core technologies for Java developers.
Problem Background and Root Causes
The "Failed to connect to remote VM. Connection refused" error during Eclipse remote debugging typically indicates that the debug client cannot establish a socket connection with the target JVM. Technically, this arises from several fundamental issues: the target server not running in debug mode, port configuration mismatches, firewall blocking connections, or the server process failing to properly initiate debug listening.
Core Configuration Elements Analysis
Successful remote debugging requires precise coordination of three key elements: correct debug port, appropriate transport protocol, and enabled debug mode in the server JVM. Port numbers must remain consistent, with common defaults being 8000 for Tomcat and 9009 for GlassFish. The transport protocol typically uses dt_socket, which is the standard Java Debug Wire Protocol.
Tomcat Server Configuration Details
For Apache Tomcat servers, configuring remote debugging requires setting specific JVM parameters during startup. In non-Windows service environments, create a debug startup script:
set JPDA_ADDRESS=8000
set JPDA_TRANSPORT=dt_socket
catalina.bat jpda startThis script sets the debug address and transport protocol, then starts Tomcat in debug mode. It's crucial to ensure the port number exactly matches the setting in Eclipse's debug configuration.
Windows Service Environment Special Handling
When Tomcat runs as a Windows service, the configuration approach differs. JVM debug parameters must be added through the Tomcat monitor program or by directly editing service configuration:
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=nThis parameter combination specifies debug transport method, listening address, server mode, and whether to pause at startup waiting for debugger connection. suspend=n means no pausing, allowing normal server startup.
GlassFish Server Configuration
For GlassFish servers, the configuration process is more graphical. Navigate through the admin console to the JVM settings section of server configuration, enable the debug option, and restart the server. This method is relatively straightforward but equally requires ensuring correct port configuration.
Eclipse Debug Configuration Verification
After proper server configuration, create or modify the remote Java application debug configuration in Eclipse. Key settings include: selecting "Standard (Socket Attach)" as connection type, setting host address to server IP (127.0.0.1 for local), and ensuring the port number exactly matches the server's debug port.
Troubleshooting and Best Practices
When connections continue to fail, follow these troubleshooting steps: first verify the server is actually listening on the specified port using netstat command; second confirm firewall settings to ensure debug port isn't blocked; finally check time synchronization between Eclipse and server to avoid connection issues due to time differences.
Supplementary Solutions
Beyond the primary methods, simple Eclipse restart can sometimes resolve temporary connection issues, particularly after extended development sessions. This can clear potential memory leaks or state inconsistency problems.