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 138070 - Able to start two GF V3 servers which are installed on same machine and have same ports(4848,8080,8181)
Summary: Able to start two GF V3 servers which are installed on same machine and have ...
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Sun Windows XP
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 145078 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-24 11:57 UTC by dpkumar
Modified: 2008-09-24 06:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 dpkumar 2008-06-24 11:57:00 UTC 
NB Build:NetBeans IDE Build 200806230002
JDK:1.6.0_06

Steps to reproduce:
1.Install NB build.
2.Check the default GlassFish V3 server under servers node.
2.Now Right click on the server node select GlassFish V3TP2.
3.Set installation location and select Download V3 now in the "Server Location" dialog window.
4.After downloading click on FINISH.
5.Now start default GlassFish V3 server and registered GlassFish V3 TP2 server.

Both servers are using same port(4848,8181,8080). When I start second server it should not start since its using same ports.
Comment 1 _ pcw 2008-06-24 18:48:11 UTC 
You can do this via the command line (asadmin) too.  I have a query out to the server team as to whether it is a bug or
a feature :)

If you refresh the second server instance, it will no longer show as running.

I don't think this is a P2, downgrading to P3.
Comment 2 dpkumar 2008-06-25 06:26:21 UTC 
Yes, I observed on refreshing the second server instance, it will no longer show as running.
Comment 3 _ pcw 2008-06-27 20:15:34 UTC 
Filed as glassfish issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=5228

We could work around this if need be by monitoring the log for the BindExceptions and terminating the second instance by
force.  But it's better if this is fixed in the server.
Comment 4 _ pcw 2008-08-26 02:46:21 UTC 
In latest server builds (B20 onward for certain), a server experiencing BindExceptions from Grizzly on startup will
print error messages and shut itself down.

But due to the way the plugin detects server startup, the IDE still thinks the server started, so we have a bit of work
to do to fix this.
Comment 5 Vince Kraemer 2008-08-26 02:50:29 UTC 
*** Issue 145078 has been marked as a duplicate of this issue. ***
Comment 6 Vince Kraemer 2008-09-21 07:16:55 UTC 
I am working on a fix for this.
Comment 7 Vince Kraemer 2008-09-23 18:48:19 UTC 
http://hg.netbeans.org/main/rev/546e9f9f1d79 (but there is a message mix up in this commit... which I corrected in a
later commit)
Comment 8 Quality Engineering 2008-09-24 06:00:23 UTC 
Integrated into 'main-golden', will be available in build *200809240201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/546e9f9f1d79
User: vkraemer@netbeans.org
Log: #138070 : starting two servers on overlapping ports shows both as started,
     even though one of them did not start successfully.