Community
Participate
Working Groups
java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.DataInputStream.readFully(Unknown Source) at java.io.DataInputStream.readFully(Unknown Source) at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:220) at org.eclipse.jdi.internal.connect.SocketTransportService.access$1(SocketTransportService.java:216) at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) at java.lang.Thread.run(Unknown Source) -- Configuration Details -- Product: Eclipse IDE 4.12.0.20190614-1200 (org.eclipse.epp.package.jee.product)Installed Features: org.eclipse.jdt 3.18.0.v20190605-1800 Versioning Plugin: org.eclipse.platform 4.12.0.v20190605-1801
Could you please update on this issue? I am unable to do remote debugging over. I am able to telnet for the Host and port. I am able to connect through LAN however, i am only facing issue over VPN.
You can try increasing the communication timeout under Preferences->Java->Debug
I tried increasing the timeout under Preferences->Java->Debug but did not work. Observation: It is a socket timeout. It seems after verifying netstat -t log, connection gets established. However, after establishing connection it throws socket timeout exception.
The issue is only during VPN. After connecting to LAN it works fine.
I'm sorry, I believe this is your local vpn / firewall / proxy / whatever network issue, not related to the Eclipse code.
This is VPN is connected through Cisco AnyConnect Secure Mobility Client. All other firewall, proxy are disabled and still facing the issue.
Try writing a java socket program and see if it works with your VPN and it's only Eclipse which is not working!
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
