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 209294 - SEVERE: Shutting down v3 due to startup exception : No free port within range: 8080=com.sun.enterprise.v3.services.impl.monitor.MonitorableSelectorHandler@1f854bd
Summary: SEVERE: Shutting down v3 due to startup exception : No free port within range...
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: TomasKraus
URL:
Keywords:
: 209293 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-08 05:19 UTC by vkomati007
Modified: 2014-05-09 10:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 209294


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vkomati007 2012-03-08 05:19:19 UTC
Product Version = NetBeans IDE 7.0 Beta 2 (Build 201102140001)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.6.0
Runtime = Java HotSpot(TM) Client VM 1.6.0-b105
F:\LUclass\MCAI\CAlab\basics\simple\nbproject\build-impl.xml:703:
Comment 1 Marian Mirilovic 2012-03-09 08:24:16 UTC
GlassFish Server 3.1 Start Failed
Comment 2 Marian Mirilovic 2012-03-09 08:25:26 UTC
*** Bug 209293 has been marked as a duplicate of this bug. ***
Comment 3 Vince Kraemer 2012-05-17 18:38:36 UTC
is there something running on port 8080?
Comment 4 TomasKraus 2012-05-23 09:21:20 UTC
Is this really a bug? We need more details to evaluate this issue.

1) How did you installed GlassFish?
2) How did you configured GlassFish and assigned ports to listen for incoming requests?
3) Are you sure that there is no other application listening on port 8080? There should be anything else providing HTTP service (Tomcat, etc.).
Comment 5 TomasKraus 2012-11-22 10:28:33 UTC
Still missing requested information. Closing this bug now. Please feel free to reopen it if you see the problem with 7.3 or later and provide us more details.