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 147891 - [65cat] debugger tries to attach on wrong port
Summary: [65cat] debugger tries to attach on wrong port
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: REGRESSION
: 147947 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-22 15:22 UTC by gholmer
Modified: 2008-11-24 08:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gholmer 2008-09-22 15:22:22 UTC 
[ BUILD # : 200809220201 ]
[ JDK VERSION : 1.6.0_07 ]

My last successful attach with the debugger was to a Tomcat with the
debugger on port 7070.  I now want to attach to a GlassFish with the
debugger on on port 9009.

1) Click "Attach Debugger" from the toolbar icon
2) Port prompt comes up as 7070, change to 9009
3) Click OK.
4) Error message in output window says

Attaching to localhost:7070
Connection refused.
Comment 1 Daniel Prusa 2008-09-22 15:54:08 UTC 
Does it mean that the debugger tries to attach on the port specified for the previous session?
Can you try one more attempt with a different port number, please?
I am not able to reproduce it myself.
Comment 2 gholmer 2008-09-22 16:34:40 UTC 
1) changed GlassFish to listen on 9008
2) restarted GlassFish
3) restarted NetBeans
4) tried to attach on 9008
5) same results (i.e. dialog prompted for 7070, I changed it to 9008, and got the same error)

I also tried deleting the contents of var/cache in the userdir, but with the same results.
Comment 3 gholmer 2008-09-22 19:13:22 UTC 
I tried leaving the port the same (dialog comes up w/7070) and instead changing the hostname to a machine that had a
Tomcat running in debug at 7070, and it also failed.

However, when I went back to build 200809180201, it worked fine. So it appears that something broke between these two
builds.
Comment 4 Martin Entlicher 2008-09-22 22:15:59 UTC 
I've reproduced it. Unfortunately it's a regression caused by the fix of issue #138717.
Comment 5 Quy Nguyen 2008-09-23 04:30:14 UTC 
*** Issue 147947 has been marked as a duplicate of this issue. ***
Comment 6 Quy Nguyen 2008-09-23 04:31:57 UTC 
This issue also breaks the Web Page JavaScript debugger when using Attach debugger.
Comment 7 Martin Entlicher 2008-09-23 08:21:33 UTC 
Yes, it breaks all debuggers. Working on a fix...
Comment 8 Martin Entlicher 2008-09-23 08:55:43 UTC 
Fixed in changeset:   103314:7efe9f14053b
http://hg.netbeans.org/main/rev/7efe9f14053b
Comment 9 Quality Engineering 2008-09-23 18:01:21 UTC 
Integrated into 'main-golden', will be available in build *200809231435* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/7efe9f14053b
User: mentlicher@netbeans.org
Log: #147891 - We must not ask twice for the customizer. getController returns null by default and the implementation casts the customizer component instead.
Comment 10 matusdekanek 2008-11-24 08:37:26 UTC 
seems to be fine
marking as verified