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 38438 - monitor doesn't use changed internal http server port until web server restart
Summary: monitor doesn't use changed internal http server port until web server restart
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: HTTP Monitor (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-06 16:59 UTC by L Martinek
Modified: 2009-12-21 04:40 UTC (History)
0 users

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 L Martinek 2004-01-06 16:59:28 UTC 
[200401051900]

Change port number of internal http server.
Execute a JSP.
No entry will appear in monitor. If you change
port number back to 8082, monitor will work.

According to old test specification, this should
be working also in NB 3.5, but I am not sure if
it's true.
Comment 1 L Martinek 2004-01-06 17:06:43 UTC 
Above is true only for incremental deployment. If you change port
number of int. http server, stop Tomcat and execute a jsp, new int.
http server port will be used.
Comment 2 Ana.von Klopp 2004-01-06 17:15:41 UTC 
The reason this worked in the past was the server-side component of 
the monitor retrieved the port number itself by talking to a socket 
provided by the client-side component. Now, the port number is gotten 
from a filter init parameter. 

I'll reassign this to Petr for a question: is it possible to have the 
deployment descriptor reloaded during incremental deployment? If so, 
this one is yours. If not, we'll have to update the monitor spec, and 
maybe the trouble shooting section in the online help.
Comment 3 Ana.von Klopp 2004-01-06 17:16:28 UTC 
BTW, it's correct that the new behaviour was implemented in 3.5, so it 
stopped working in that release.
Comment 4 Petr Jiricka 2004-01-07 09:31:09 UTC 
I think we could find a way to dynamically refresh the port number on
the server - if it comes to worst, we can just restart the server
after the port change. Or we could design a special request that would
contain the message about the port change, and that would be caught by
the filter. However, I am not sure if this is worth the effort -
changing the internal port number is not a very common operation (most
users don't know that there is any internal server). So I'd go down
the docs change path.
Comment 5 Petr Jiricka 2004-02-17 14:12:28 UTC 
Setting target milestone to Promo D, per previous comments.
Comment 6 Petr Jiricka 2004-08-17 12:49:23 UTC 
Will not be done in Promo D, setting target milestone to Promo E.
Comment 7 Sherold Dev 2005-10-21 13:58:56 UTC 
TM -> 5.0
Comment 8 Petr Blaha 2006-03-13 13:58:01 UTC 
TM 5.0 -> TBD
Comment 9 Sherold Dev 2006-05-31 14:26:20 UTC 
making this a p4, since this use-case is not very common and no user has had
problem with this as far as I know
Comment 10 Quality Engineering 2009-12-21 04:40:03 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team