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 152259 - [65cat] [dbg] Glassfish V3 should offer better control over the HTTP port to avoid conflicts.
Summary: [65cat] [dbg] Glassfish V3 should offer better control over the HTTP port to ...
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-04 05:16 UTC by esmithbss
Modified: 2013-11-08 13:55 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
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 esmithbss 2008-11-04 05:16:48 UTC 
[ BUILD # : RC-2 ]
[ JDK VERSION : 1.6.0_07 ]

I already have Glassfish V2 on the default ports (4848, 8080, etc...)
installed on my box and am trying to debug a Ruby program which is
trying to launch Glassfish V3 on port 8080.

Apparently, there is no way to change the port Glassfish V3 is
running against within the IDE.

Changing the value in the project properties does nothing.

And the server command line in the Tools->Servers property dialog
cannot be changed.

Effectively this renders Glassfish V3 unusable on machines with port
8080 already in use.
Comment 1 _ pcw 2008-11-04 05:26:20 UTC 
--> serverplugins/glassfish_v3

I am going to change this an enhancement asking "For better control of the ports used by V3."  We have improvements
lined for 7.0, but we did the best we could for 6.5.

You can do one of two things:

1) Remove the current default V3 server domain.  Modify domain.xml for that server domain (in
glassfish/domains/domain1/config/domain.xml) and change the http port from 8080 to whatever you want.  Search the file
for "8080" and you'll find the http-listener element where this is set.

2) Use the "Add Server" wizard to add a new V3 instance based on a personal domain (on the last panel of the wizard,
just type in a new domain name and a new domain will be created with randomized open ports.  Note the HTTP port
displayed in the output window.
Comment 2 _ pcw 2008-11-04 05:27:51 UTC 
Changing summary to properly reflect what this enhancement is asking for.
Comment 3 _ pcw 2008-11-04 05:30:57 UTC 
Lastly, I must point out that when debugging a ruby application running on V3, we don't actually run the full server on
the standard HTTP port (described above) -- why is a long story.

It uses the port specified in the Project | Properties dialog for the Rails project (but really ought to be incrementing
that value to the first free port, e.g. 8081 or something).  Normally that value is set to 3000 since that is what
Webrick users are used to.  Change it to whatever you want and for debugging Rails apps on V3, that is the port that
will be used.

This will also hopefully be cleaned up considerably in 7.0.
Comment 4 Vince Kraemer 2009-12-10 12:55:18 UTC 
no bug should be assigned to issues. distributing the load.
Comment 5 Vince Kraemer 2010-02-04 12:21:09 UTC 
shift to me.
Comment 6 TomasKraus 2013-11-08 13:55:10 UTC 
HTTP listener should be modified from GlassFish admin console. NetBeans plugin is reading domain.xml file to retrieve HTTP port numbers after start. But it shall not modify it.

Changing HTTP listeners ports from netbeans UI is not a good idea. GlassFish plugin purpose is to read ionformation from Glassfish and to provide it to other NetBeans components. Only very limited set of updates back to server is allowed here and they are related to application life cycle.