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 164781 - IllegalArgumentException: Port value out of range: -11
Summary: IllegalArgumentException: Port value out of range: -11
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Rails (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@ruby
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 16:25 UTC by Oleg Khokhlov
Modified: 2011-01-28 20:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 150848

Attachments
stacktrace (3.50 KB, text/plain)
2009-05-08 16:25 UTC, Oleg Khokhlov 		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 Oleg Khokhlov 2009-05-08 16:25:17 UTC 
Build: NetBeans IDE Dev (Build 200905080201)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Windows XP, 5.1, x86

User Comments:
ovk: incorrect port number entered (server port for rails app)



Stacktrace: 
java.lang.IllegalArgumentException: Port value out of range: -11
        at java.net.ServerSocket.<init>(ServerSocket.java:180)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at org.netbeans.modules.ruby.railsprojects.server.RailsServerManager.checkIsPortInUseUsingServerSocket(RailsServerManager.java:500)
        at org.netbeans.modules.ruby.railsprojects.server.RailsServerManager.isPortInUse(RailsServerManager.java:523)
        at org.netbeans.modules.ruby.railsprojects.server.RailsServerManager.ensurePortAvailable(RailsServerManager.java:343)
        at org.netbeans.modules.ruby.railsprojects.server.RailsServerManager.ensureRunning(RailsServerManager.java:261)
Comment 1 Oleg Khokhlov 2009-05-08 16:25:51 UTC 
Created attachment 81818 [details]
stacktrace
Comment 2 Erno Mononen 2009-05-21 15:21:48 UTC 
The use case doesn't seem too common, so downgrading to P4.