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.
NBI build: 200704260000 WinXP JDk 1.6 I added around 5-6 external tomcat servers with various configurations. I created a J2ee1.4 app with a button and deployed it on tomcat5.5.17. Then I changed the target server of the application without stopping the first server. When I look at the icons of the server nodes in the runtime tab all of them are running. Steps to reproduce: Use a fresh user dir: 1.Add 2 or more external tomcat servers. 2.Create a new VWP project with one of the Tomcat5.5 servers as the target. 3.Place a button on the page. 4.Deploy the application 5.Without stopping the first tomcat server change the target server of the project to another tomcat5.5 server. 6.Run the application. At this point ideally it should give an error that there was a port conflict since an instance is already running at that port. Instead the application runs and shows the page in a browser. Now if you check the servers node in the runtime tab you will see that all of the servers show a green running icon on them. In addition the all server nodes can be expanded to view their web applications. Even though they show the same applications. If you stop any one of them it will stop the first server and you wont be able to open the page in browser even though the first server node will show that it is running. Interestingly the glassfish node does not show that it is running. I am attaching the screenshot of the server nodes as well.
Created attachment 41757 [details] server nodes screenshot
Yes, this is a known issue. I know for sure that it has been so since NetBeans 3.6 and probably even before that. On one hand it is an obvious bug, I agree. On the other hand I have never seen any user complains about this, only from QA, NetBeans developers and doc writers. Maybe because typically users typically use one server on one machine. If not they typically know that each server needs to use a different port and if you set a different port this issue will go away. This is why I am downgrading it to P3. Unless Stepan has been planning to work on this area lately I think this is "future".
this probably belongs over in tomcatint
*** This issue has been marked as a duplicate of 98386 ***