Community
Participate
Working Groups
When launching eclipse java debugger in socket_listen mode it would be very useful if the debugger restarted after a connected JVM disconnects. Use case: java based distributed computing applications run small chunks of java work which finish and terminate. java command line args can be added for the processes so it connects to a socket_listen eclipse java debug but once the process finishes the eclipse java debugger stops. after the first task finishes, a new task is spawned with a new small unit of work but same command line args as the previous. since the java debugging instance is no longer listening, the process can't connect. As a specific example apache Hadoop often launches >1000 java tasks for each job. It's desirable to trace/debug into these tasks and the easiest method is to set the eclipse debugger into socket_listen and add command line params to the java tasks to connect to the eclipse debugger. once the task dies the debugger stops and the next task is unable to connect. since the tasks launch programmatically there's no opportunity to pause hadoop to restart the eclipse debugger. if the eclipse debugger restarted after the JVM disconnected this would no longer be an issue.
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.
