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.
1. Port 8080 should be occupied. 2. Run installer. Result: GlassFish's port is changed to 8081 and if port is changed to 8080, appropriate message will appear. But there is no possibility to change port for Tomcat and even 8080 is occupied, Tomcat's port is 8080.
Jano, should we add port configuration functionality (and messaging) for Tomcat in the same way as for glassfish? Unfortunately tomcat configuration is not reflected in the current UI spec at all. Stepan, What should be done for setting non-default port (not 8080) for tomcat? Ws conf/server.xml file the only one that should be updated for that? What other ports are used by tomcat and should be checked during tomcat configuration for occupation? Jano, Stepan, What other data (ports/login/password/?) is worth to be configured? Dmitry
If you are using Tomcat plugin's auto-registration functionality, the server port will be 8084. For more info refer to http://wiki.netbeans.org/wiki/view/TomcatAutoRegistration There are three ports which Tomcat server might use: server port, shutdown port and debug port. If you would like to configure Tomcat ports from the installer, the Tomcat plugin would have to provide some support for it, currently there is none.
BTW, there should be no port conflict between auto-registered Tomcat and GlassFish. I don't think this is really a valid issue. It might be an enhancement, though.
Yes, we use auto-registration functionality in the installer.
Yes, definitely default port is 8084. But what if 8084 also will be occupied by some other process.
Sure, it is possible, although not very likely. I'm not saying it is not a nice to have feature, but there is still a chance to change the server port later in the server manager.
If the user can change ports in the IDE, then I don't think it's very important to provide customization in the installer. Simpler installer is better. Hopefully a descriptive error message appears if the port number is already used and Tomcat cannot start, so that the user knows what to do (go to the Server manger and change the port number).