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.
The tomcat integration module should check whether the ports required to run the server (admin & connectors) are available before it starts the server. Currently if a port is taken, the server tries to start but throws a bind exeception which we report on the output pane. This is not very helpful behaviour. This issue keeps coming up over and over again, and the nature of the problem is clearly not obvious to a lot of users as we get a lot of queries about this.
Do you really think that we should check all the Tomcat4.0 ports for availability ? What does it mean : Befor starting execution we should check every Tomcat4.0 port for availability - server port and all <Connector> ports. Probably the easiest way is try to create ServerSockets on these ports before the execution. - this will probably slower again the execution - there are problems with closing sockets on Linux Is it reasonable to add another additional tests before the Tomcat execution? I think we did much for users when we changed all port numbers in the "internal" Tomcat installation. (In order not to clash with an external installation). If user is advanced enough to play with different Tomcat installations, he will be able, I think, to avoid the 'port clash' or to understand the source of problem from the error message in Output Window. As the Tomcat runs as an external process (in different JVM), it is difficult to handle its java.net.BindExceptions in IDE.
Fixed for FCS. Testing these ports for availability : - the port of the targeted host (Tomcat instance) - the admin port
VERIFIED