This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Running even the most trivial programming - set a breakpoint at the first executable statement. Run with the debugger. The following is output using JDK 1.6 debug: FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) ERROR: transport error 202: connect failed: Connection refused ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690] Java Result: 134 BUILD SUCCESSFUL (total time: 7 seconds) If I use JDK 1.5 the output looks like: debug: ERROR: transport error 202: connect failed: Connection refused ["transport.c",L41] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedJava Result: 134 BUILD SUCCESSFUL (total time: 2 seconds) On the same machine, running the program using Netbeans 6.1, the debugger works flawlessly. Dave
I had the same problems also on Mac OS X 10.5. For reasons I do not fully understand my Mac named "noname" had received an updated DHCP address ...108 but somehow the Mac OS DNS still resolved "noname" to the previously issued ...102. As the exact hostname and port are given on the start of the application the connection between debugger and application failed. A reboot resolved the issue for me. The following two conditions may be sufficient to re-produce the fault: - mac has a hostname assigned - dhcp update has happened Workaround may be: - use localhost if localhost is meant Other lesson learned: - some more transparency in the debugger/JVM options in Netbeans will help. I had to use "ps -ef" to understand what Netbeans was doing. My take on it: Mac issue but NetBeans could do better.
Thanks for the description, I'll add a workaround to NetBeans to use localhost if the host address is not usable. *** This issue has been marked as a duplicate of 154974 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.