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.
I tried to attach the debugger using socket attach. The correct port was 50113, but I accidentaly entered 501113. The debugger throwed the following exception: java.lang.IllegalArgumentException: port out of range:501113 at java.net.InetSocketAddress.<init>(InetSocketAddress.java:118) at com.sun.tools.jdi.SocketTransportService.attach(SocketTransportService.java:201) 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:208) at org.netbeans.modules.debugger.jpda.actions.StartActionProvider.doStartDebugger(StartActionProvider.java:189) at org.netbeans.modules.debugger.jpda.actions.StartActionProvider.access$100(StartActionProvider.java:75) at org.netbeans.modules.debugger.jpda.actions.StartActionProvider$1.run(StartActionProvider.java:165) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986) I know that it was my mistake, but the debugger should handle these situations more gracefully e.g. not to throw an exception.
This is a defect in JDI code. I've submitted this as #6707297, it will be available at http://bugs.sun.com/view_bug.do?bug_id=6707297.
*** Issue 139164 has been marked as a duplicate of this issue. ***
Can this not be easily fixed just by simple check if the number is not larger than 65535?
This is basically a user error. And this behavior was in the code from the very beginning. I do not consider this to be important enough to add extra checks in NetBeans code, it should be fixed in JDI code. It can be as easily fixed there.
*** Issue 145743 has been marked as a duplicate of this issue. ***
*** Issue 170442 has been marked as a duplicate of this issue. ***
*** Bug 179207 has been marked as a duplicate of this bug. ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.
*** Bug 235619 has been marked as a duplicate of this bug. ***