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.
Im trying to debug a simple Java 1.6 application under Fedora 10 with Netbeans 6.5. The debugger appears to start (the view is changed to debugger mode) but no threads are started. The debugger will just sit there waiting for the application to load.
Please, can you be more specific? We need more information since debugger starts fine for us in NetBeans 6.5. Is there anything in the Debugger Console? Can you provide some sample application with which we can reproduce this problem? Are there any breakpoints in the Breakpoints window (e.g. thread breakpoints which would pause the application as soon as a thread is started, etc.)?
A simple Hello world app would do: 1 public class Main { 2 public static void main(String[] args) { 3 for(int i=0; i<10; i++){ 4 System.out.println("Hello world!"); 5 } 6 } 7 8 } I set the breakpoint on line 3: The breakpoint window shows the line of the breakpoint The watches, local variable and call stack windows are empty The output window shows: "Listening on 45393" After 3 minutes I get: ERROR: transport error 202: connect failed: Connection timed out FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) 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: 1
similar to issue 148442
The latests updates do not fix this =(
I've tested this with Netbeans 7.0 M1 and the bug still exists
Well, I do not think this can be fixed in NetBeans. Can you please try if you can attach debugger on command-line to an application started in debug mode? Can you verify whether localhost works and whether some firewall does not block access to it?
I've found out something that might help. I tried running netbeans from the console to see if something might point to the error.When I try to debug my stand alone project the console output gives me this: WARNING [org.netbeans.modules.parsing.impl.TaskProcessor]: Source.runUserTask called in AWT event thread by: org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:173) INFO [org.netbeans.modules.j2ee.deployment.impl.ServerInstance]: DebuggerInfo cannot be found for: GlassFish V3 INFO [org.netbeans.modules.j2ee.deployment.impl.ServerInstance]: DebuggerInfo cannot be found for: GlassFish V2 INFO [org.netbeans.modules.j2ee.deployment.impl.ServerInstance]: DebuggerInfo cannot be found for: Apache Tomcat 6.0.18 so I started looking and found this: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5094485 hope it helps
I've run the debugger as shown here: (FOR LINUX) % java -Xdebug -Xrunjdwp:transport=dt_socket,address=5555,server=y,suspend=n MyClass With no problems. However if I try to run it like this: (FOR WINDOWS) %j ava -agentlib:jdwp=transport=dt_shmem,address=jdbconn,server=y,suspend=n MyClass I get the same error as before (with netbeans). Maybe Fedora is not telling NB that its a linux computer?
i've got the same error if i try to launch debug test on a maven project in NetBeans 6.7 beta on macosx, but: 1) if i launch on a shell mvn jetty:run (to run a webapp) with these parameters export MAVEN_OPTS="-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n" then i can attach the netbeans debugger and use it correctly. 2) if i run (and debug) my project not in test mode, the netbeans debugger works properly
Without any additional information for long time (+ probably not a netbeans issue) - INVALID. We can't do anything in this case. Reporter, please try latest netbeans (6.7.1 or 6.8 dev). If the problem persists, please add relevant information and reopen issue. Thanks in advance.
closing incomplete issues