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.

Bug 50825 - [40cat] JPDA debugger does not start
Summary: [40cat] JPDA debugger does not start
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
: 50849 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-25 19:34 UTC by jasondonmoyer
Modified: 2005-07-11 08:01 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exception from log file (599 bytes, text/plain)
2004-10-25 19:36 UTC, jasondonmoyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jasondonmoyer 2004-10-25 19:34:02 UTC
[ BUILD # : 200410241800 ]
[ JDK VERSION : J2SE 1.5.0 ]

When trying to start the debugger, I get
'Attaching to jdonmoyer-t30:8787' in the output
window, but it never connects.

I get an exception in the log saying that a
timeout has occurred.  I bumped up the timeout in
the JPDA debugger dialog and I still get the
exception (even before the timeout should have
elapsed).  Leaving everything else unchanged, the
debugger startsin the prior daily build.
Comment 1 jasondonmoyer 2004-10-25 19:36:26 UTC
Created attachment 18497 [details]
exception from log file
Comment 2 Maros Sandor 2004-10-26 09:04:21 UTC
Works for me on today's sources. It seems you are attaching to a 
nonexistent process. Please provide more information about what you 
do:

1) JVM parameters that you use to start debugee
2) exact steps in NB that you do in order to attach to debugee

It is important to verify that jdonmoyer-t30 resolves to a valid IP 
and that debugee listens on this interface. You can use telnet 
command to do this: "telnet jdonmoyer-t30 8787". If telnet fails to 
connect, debugee was not started properly.
Comment 3 zikmund 2004-10-26 13:22:19 UTC
Probably connected to issue 50849 (Can't debug WebApp).
Comment 4 jasondonmoyer 2004-10-26 14:46:37 UTC
>It seems you are attaching to a nonexistent process.

As I stated in my initial report, this is obviously not the case. 
Leaving everything else unchanged (closing the 10/24 build and opening
the 10/20 build using the same user directory and therefore the same
parameters for connecting works correctly).

All I do is hit the debug button in the toolbar and click ok on my
preconfigured JPDA settings dialog.

I'll try in the latest build.
Comment 5 jasondonmoyer 2004-10-26 15:24:38 UTC
Same behavior occurs in 200410251800.  Also issue 50849 looks to be
the same problem.
Comment 6 Maros Sandor 2004-10-26 16:19:51 UTC
Fixed attaching connector that waited for vmstart event that never 
arrives.

/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/actions/Start
ActionProvider.java,v  <--  StartActionProvider.java
new revision: 1.11; previous revision: 1.10
Comment 7 Maros Sandor 2004-10-26 16:20:22 UTC
*** Issue 50849 has been marked as a duplicate of this issue. ***
Comment 8 jasondonmoyer 2004-10-26 16:30:33 UTC
If someone can make a patch that will work with the 200410251800 daily
build, I'll verify the fix and ask Jiri to remove it from the list of
showstoppers for the final Q-build. 
Comment 9 jasondonmoyer 2004-10-27 15:08:53 UTC
Verified fixed in 200410261800 daily
Comment 10 Vladimir Hudec 2004-12-17 18:05:51 UTC
I have the same problem with final nb 4.0 release,
trying to debug simple web application, I can see a message

/home/vlado/working/WebApplication3/nbproject/build-impl.xml:295:
org.netbeans.api.debugger.jpda.DebuggerStartException: Connection refused

running on SuSE Linux 9.1, JDK 1.2.4_06
Comment 11 Jan Jancura 2004-12-20 14:45:34 UTC
Can not reproduce. Is it regular or random?
Comment 12 jasondonmoyer 2004-12-20 14:59:42 UTC
The original issue works fine for me on the 4.0 release.  It looks
like Vladimir's issue may be different... He's getting a Connection
Refused (rather than a timeout) and it also appears to be coming from
the ant script (not from running the debugger inside the IDE)
Comment 13 Vladimir Hudec 2004-12-21 07:35:18 UTC
How to reproduce te problem:

1. install SuSE 9.1 with the latest fixes
2. install the nb 4.0
3. generate simple web application using nb 4.0 wizard
4. debug the generated web application

The exception in nb log is the next one:
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:452)
        at java.net.Socket.connect(Socket.java:402)
        at java.net.Socket.<init>(Socket.java:309)
        at java.net.Socket.<init>(Socket.java:124)
        at
com.sun.tools.jdi.SocketTransport.attach(SocketTransport.java:46)
        at
com.sun.tools.jdi.SocketAttachingConnector.attach(SocketAttachingConnector.java:65)
        at
org.netbeans.api.debugger.jpda.AttachingDICookie.getVirtualMachine(AttachingDICookie.java:180)
        at
org.netbeans.modules.debugger.jpda.actions.StartActionProvider$1.run(StartActionProvider.java:80)
        at java.lang.Thread.run(Thread.java:534)

Change of debug port doens't help. Internal firewall isn't running.
Comment 14 Jan Jancura 2005-02-04 08:19:46 UTC
Its chaotic now. Original issue is fixed on 4.0, as Jason wrote.
Web related problem is fixed too
(50849)
------ Additional Comments From zikmund 2004-10-27 02:06 PDT -------

Verified fix in build 200410261800.

So, I am closint this "umbrella" one.
Zikmund, if its still reproducible create a new issue for proper
OS&description, please.
Comment 15 Max Sauer 2005-07-11 08:01:26 UTC
In nbdev2005007061800 this issue does not occure, therefore I'm closing this.