JDK 1.5 b3

*** Issue 47887 has been marked as a duplicate of this issue. ***

Reproduced on build 200408311800 on java 1.5.0_rc-b63 on Win XP Pro

Debugger started listening on port, but handshake with debugged
applcation failed. It was possible to connect to debugger on the port
via telnet command.

OUTPUT:

init:
deps-jar:
compile:
ERROR: transport error 202: recv failed during handshake: Connection
reset by peer ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) ["debugInit.c",L497]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
Java Result: 1
debug:
BUILD SUCCESSFUL (total time: 0 seconds)

*** Issue 49566 has been marked as a duplicate of this issue. ***

I was getting this error:

FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)
ERROR: transport error 202: connect failed: Connection refused
["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) ["debugInit.c",L497]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
Java Result: 1

on Windows XP Home (Netbeans 4.0 Beta 2). However for me the problem
went away when I altered the Norton Personal Firewall settings for
java.exe to allow all access. Could just be coincidence, but turning
the firewall settings from permit to block caused the debugger problem
to reappear, and permitting firewall access again caused the debugger
to start working. I'm a new user so this may be history to the rest of
you.

Comment from another user on nbusers:

------------------

FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)

ERROR: transport error 202: recv failed during handshake: Connection
reset by peer ["transport.c",L41]

ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) ["debugInit.c",L497]

JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized

Java Result: 1

------------------

From number number of reports and duplicates doesn't seem to be so
random. Is there any comment from Mr. Developer? It would be highly
appreciated.

Hello Mr.Kubec.
Random means that bug is not regulary reproducible, which is this case.
This bug probably occurres during start of java.exe task from ant
build script. So, its probably not caused by debugger code. 
But we do not have testcase to fire this bug to JDK. I am working on it.

I was able to reproduce this issue, but it seems to be a user error:

here us the repo:

bash-2.05b$ cat hi.java
public class hi {

   public static void main(String args[]) {

      System.out.println("hi");

   }
}

bash-2.05b$ java -fullversion
java full version "1.5.0-b64"

bash-2.05b$ java
-Xrunjdwp:transport=dt_socket,address=4321,suspend=y,timeout=10000 hi
ERROR: transport error 202: connect failed: winsock error 0
["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) ["debugInit.c",L497]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports
initializedFATAL ERROR
in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)

But if I add "server=y" to the runjdwp option, everything works:

bash-2.05b$ java
-Xrunjdwp:transport=dt_socket,address=4321,server=y,suspend=y,
timeout=10000 hi
Listening for transport dt_socket at address: 4321

I discovered this when trying to create a free form ant project.  Much
more documentation is needed for debugging in netbeans with the new
ant build system.  

http://www.netbeans.org/kb/articles/freeform-config-40.html

is a good start, but needs much more elaboration.

For instance, when I try and connect to my program with the debugger I
get this error:

sh-2.05b$ java
-Xrunjdwp:transport=dt_socket,address=4321,server=y,suspend=y,
timeout=10000 hi
Listening for transport dt_socket at address: 4321
ERROR: transport error 202: recv failed during handshake: Resource
temporarily unavailable ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or
fatal error

This can be fixed, but getting the debugger to work can be a painful
process.  There should be a netbeans debugging FAQ that addresses jdk
debugging problems as well as netbeans debugging problems, especially
since there were such drastic changes to the debugging interface in
jdk1.5.

Not reproducible with current build. Probably fixed while making 
changes in synchronization. 

I've seen that error on and NB 4.1 Q-build 200503150955
this is JDK 1.5.0_02, Win2K, dual CPU. So I'm reopening.
The other error occured when I try to stop or restart
(not sure) after the first error, so it's probably a
consequence of the first one, or related in some other way.

 init:
 deps-jar:
 compile:
 FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)
 ERROR: transport error 202: connect failed: Connection refused ["transport.c",L41]
 ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
["debugInit.c",L497]
 JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
 Java Result: 1
 debug:
 BUILD SUCCESSFUL (total time: 2 seconds)

I got the above error twice in a row.
Here is another one (without restarting NB). 
It seem that my NB process has serious problems:

 init:
 deps-jar:
 compile:
 java.lang.IllegalThreadStateException
   at java.lang.ThreadGroup.add(ThreadGroup.java:856)
   at java.lang.Thread.start(Thread.java:573)
   at
org.apache.tools.ant.taskdefs.ProcessDestroyer.removeShutdownHook(ProcessDestroyer.java:145)
   at
org.apache.tools.ant.taskdefs.ProcessDestroyer.remove(ProcessDestroyer.java:198)
   at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:487)
   at org.apache.tools.ant.taskdefs.Java.fork(Java.java:746)
   at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:170)
   at org.apache.tools.ant.taskdefs.Java.execute(Java.java:83)
   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
   at org.apache.tools.ant.Task.perform(Task.java:364)
   at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
   at org.apache.tools.ant.Task.perform(Task.java:364)
   at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:377)
   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
   at org.apache.tools.ant.Task.perform(Task.java:364)
   at org.apache.tools.ant.Target.execute(Target.java:341)
   at org.apache.tools.ant.Target.performTasks(Target.java:369)
   at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
   at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
   at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
   at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
   at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
 debug:
 BUILD SUCCESSFUL (total time: 13 seconds) 

Yes, debugger starting problem reapeared few days ago and should be fixed now
(verified by submitters). Please, try current build. Thanks.

Not reproducible with current build. See above...

Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.