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 192925 - IllegalArgumentException: unable to parse port number in address
Summary: IllegalArgumentException: unable to parse port number in address
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-06 15:19 UTC by Tomas Danek
Modified: 2010-12-06 17:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 68313

Attachments
stacktrace (933 bytes, text/plain)
2010-12-06 15:19 UTC, Tomas Danek 		Details
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 Tomas Danek 2010-12-06 15:19:03 UTC 
Build: NetBeans IDE Dev (Build 201012060001)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03-307, Java(TM) SE Runtime Environment, 1.6.0_22-b04-307-10M3261
OS: Mac OS X

User Comments:
musilt2: forgot "http://" in remote sever. My fault, but could be handled more gracefully.




Stacktrace: 
java.lang.IllegalArgumentException: unable to parse port number in address
   at com.sun.tools.jdi.SocketTransportService.attach(SocketTransportService.java:194)
   at com.sun.tools.jdi.GenericAttachingConnector.attach(GenericAttachingConnector.java:98)
   at com.sun.tools.jdi.SocketAttachingConnector.attach(SocketAttachingConnector.java:72)
   at org.netbeans.api.debugger.jpda.AttachingDICookie.getVirtualMachine(AttachingDICookie.java:223)
   at org.netbeans.modules.debugger.jpda.actions.StartActionProvider.doStartDebugger(StartActionProvider.java:185)
   at org.netbeans.modules.debugger.jpda.actions.StartActionProvider.access$200(StartActionProvider.java:81)
Comment 1 Tomas Danek 2010-12-06 15:19:07 UTC 
Created attachment 103624 [details]
stacktrace
Comment 2 Martin Entlicher 2010-12-06 17:09:46 UTC 
Yes, could be handled more gracefully - in JDK!
We call Argument.isValid() on each entry. That passes, but then IllegalArgumentException - this is a bug in the validation algorithm.

I've submitted bug for JDK: 7004883 that might be publicly available at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7004883