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.
General policy is not to initialize unneceseary things during startup. Opening ServerSocket doesn't look like high priority task. Many users may never touch related functionality but they are affected by its initialization. I suggest either to postpone init phase until the moment when it becames apparent that it is required or schedule this with _low_ priority to future like openfile server in utilities module Also current code doesn't handle conflicts well and HTTP monitor is not able to work properly if I run two IDE instances.
The reason for the socket server is to allow web servers used for execution to discover the IDE instance from whence the request came. However, the current solution means that it's only possible to run one instance of the client per host, which is incorrect also. I can't find the bug id for that (may be logged in bugtraq but I thought I moved those). I meant to fix this for S1S4/NB3.4, but it involves changes to several modules so we decided it was too risky.
Tegal planning
I will remove the socket as soon as the tomcatint module can declare the host. The work for the filter to read the parameters is already complete.
You can write the patch for tomcatint to declare anything you need. Just find the part of code where monitor specific stuff is handled (set or unset from server.xml) and add what you need. Sorry but from your description it is not clear to me what to do and Milan can't help you just now.
The port number is now declared in the monitor filter. Please check the next continuous build; it will contain the change.
The server socket is o longer used since the monitor server side component is notified of the internal HTTP server port during startup.
VERIFIED