JDK-8016154 : Regression: Eclipse gui java debugger does not work under 7.0_21
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7u21,8
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2013-06-07
  • Updated: 2013-09-12
  • Resolved: 2013-07-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7u40Resolved
Related Reports
Duplicate :  
Description
 to reproduce, go to Java Control Panel > Java Tab > View... > Runtime 
 Parameters 
 add this sting and save: 
 -agentlib:jdwp=transport=dt_socket,address=2502,server=y,suspend=n 
 launch a java applet in any browser. 
 attempt to remote debug from any IDE. 
 From eclipse you can do these steps: 
 Debug Configurations > New Remote Java Application > Connect tab 
 Connection Type: Standard(Socket Attach) 
 Host: localhost (assuming that you're running browser & applet on same system 
 you're debugging from, else use system name or IP address) 
 Port: 2502 (just make sure it matches Java Runtime Parameters) 
 Apply and debug. 
 . 
 I found this worked on Java 1.7_17  64 bit and 32 bit 
 uninstalled all versions of Java and installed Java 1.7_21 64 bit and 32 bit 
 . 
 these same steps to debug no longer work, connection will be refused. 
 . 
 once again uninstalled all versions of java and installed Java 1.7_17 64 bit 
 and 32 bit. 
 . 
 Once again I'm able to debug 
 . 
 Impact: This is preventing developers from updating their systems to Java 
 1.7_21 and we're forced to stay on Java 1.7_17. We're unable to take the 
 latest(and most secure) Java version. 
Comments
Removed critical watch as this is resolved in 7u40 via 8016005
24-07-2013

If this is a dup - can we close this and remove the critical-watch label?
24-07-2013

duplicate of 8016005
02-07-2013

061213 - Fix verified by Kronos. Sust. working to code-review and integrate in 7u-dev - Support asking for this fix in next public release, added 7u40-critical-watch
12-06-2013