Community
Participate
Working Groups
Build ID: M20060921-0945 Steps To Reproduce: Start a "Remote Java Application" debugging session. Connect to a remote Java app that accepts the connection and starts trading debug packets, but slowly enough that Eclipse times out. More information: After the timeout, the remote session disappears from the "Debug" window, but the TCP connection remains open. This can be verified from the remote VM or by using "netstat -an | grep ESTABLISHED" on the Eclipse side. Issue #1: the timeout should be configurable, in case you're debugging over a slow connection or on a heavily-loaded remote system. Issue #2: the socket doesn't close. This means the remote VM will not be listening for a new connection, so you can't retry without killing and restarting one side. It appears that Eclipse is timing out N seconds after the initial connection is established, rather than N seconds after the most-recently-received packet. If this is the case, it might make sense to have receipt of a response reset the timeout. I haven't investigated this behavior though.
> Issue #1: the timeout should be configurable, in case you're debugging over a > slow connection or on a heavily-loaded remote system. This is configurable on the "Java > Debug" preference page. You can control the debugger timeout (timeout for each JDWP request), and the launch (connect) timeout.
We should try to always close the socket when the debug sessions ends (and is removed). Marking as a bug day candidate.
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.
