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 170985 - IllegalArgumentException: unable to parse port number in address
Summary: IllegalArgumentException: unable to parse port number in address
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@debugger
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-27 12:53 UTC by jonycus
Modified: 2010-05-06 11:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 55009


Attachments
stacktrace (1.07 KB, text/plain)
2009-08-27 12:53 UTC, jonycus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jonycus 2009-08-27 12:53:46 UTC
Build: NetBeans IDE 6.7.1 (Build 200907230233)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows 7, 6.1, x86

User Comments:
jonycus: trying to atach socke tlistener debuger



Stacktrace: 
java.lang.IllegalArgumentException: unable to parse port number in address
        at com.sun.tools.jdi.SocketTransportService.startListening(SocketTransportService.java:261)
        at com.sun.tools.jdi.GenericListeningConnector.startListening(GenericListeningConnector.java:96)
        at com.sun.tools.jdi.SocketListeningConnector.startListening(SocketListeningConnector.java:67)
        at com.sun.tools.jdi.GenericListeningConnector.accept(GenericListeningConnector.java:143)
        at org.netbeans.api.debugger.jpda.ListeningDICookie.getVirtualMachine(ListeningDICookie.java:232)
        at org.netbeans.modules.debugger.jpda.actions.StartActionProvider.doStartDebugger(StartActionProvider.java:187)
Comment 1 jonycus 2009-08-27 12:53:52 UTC
Created attachment 86727 [details]
stacktrace
Comment 2 Martin Entlicher 2009-08-27 13:22:05 UTC
Can you please provide the port number that you have filled in in the attach dialog?
The dialog has checks that does not permit you to proceed with wrong numbers, so I wonder how did you manage to get this
exception...
Comment 3 Marian Mirilovic 2010-05-06 11:51:37 UTC
closing incomplete issues