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.
It has been discussed whether there is a way to prevent clashes of tomcat (and possibly) appserver ports during the j2ee functionality review in issue 52155. Reviewers saw a solution to this problem for servers started from the ide (e.g. those that are going to be used by unexperienced users like me and constitute most of the out of box experience): Whenever the bundled tomcat is about to be started from the IDE, the ide can try to allocate new port, get its number and close it (new SocketServer(); getPort(); close()) prior starting the tomcat. Then the port number can be passed to the tomcat, which greatly reduce the possibility of port conflict.
Not a good practice in server side development. I suggest closing as WONTFIX.
NeTbeans should not become a sys-admin tool for multi user environment... It's very hard to develop or use more than one server, on a server machine. Agree with wonfix status. At one point of time, Solaris ZONES should help isolating servers developers on a single machine server to be effective.
Agreed with Ludo and Petr, this is not very high priority.
Either there is some miscommunication or Pavel's opinion changed significantly since the confcall review. "Not a good practice in server side development" - what is not good practice? If your IDE works without problem? I am affraid that this is the goal. "It's very hard to develop or use more than one server, on a server machine." - It is hard because currently our IDE will not resolve port conflicts even it could in the most often case. "ZONES" - waiting for something misterious while having ready to implement solution is not the most benefitial strategy for end users. I have not filled the issue, just because I wanted, but because during the review confcall Pavel agreed that this is good idea. I'd like to at least hear explaination why his mind has changed and why this is no longer better for new comming users of the IDE.
Won't this require a new API in J2eeServer? Some application servers may not support "changing" the port configuration from session to session? Some may not need a port configuration change... The plugin would need a way to signal its "support" of this new feature.
moving to tomcat. (could be j2eeserver, but should not be j2ee) For the app server: 1/ the create-domain command (used in the ide) detects port conflicts 2/ the app server runtime, at boot time detects port conflicts ans uses the loggin mechanism to tell the user. solaris zones are not mysterious and there to solve this type of conflict on a big solaris system, and shield applications from the share environment constrainsts. Anyway, I still believe this issue is way beoynd the Tools or NetBeans, and is a system issue when many users and many server runtimes share the same resource. All the cli tools, admin gui tools that create and manage these runtimes have to deal with the same error detection and reporting and confifuration than what is described in the bug description.
I did not change my opinion. I agree this is a nice idea to make it work out of the box. I jsut do not think this is very important - nice to have for me.
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