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.
[20040114] There is a minor issue concerning deployment process. If there is running another (externally started or a one which survived IDE crash) tomcat server there may be a problem with deployment. Try these steps: 1) start your externall tomcat5 server (not the one from IDE) on for example 8080 port. 2) start IDE 3) create/mount a webmodule 4) try to deploy it (on default tomcat server instance [8080 port]) During the deployment you are connection the manager app on the server port (8080) and so in fact you connect to the externally started one! Simple suggestion: I guess its possible by a Process to test if the server you are connecting to is the one run from IDE. I do not exactly know all circumstances but sometimes the deployment on the external server fails!?
I am not quite sure what to do with this problem. If there was a different server we should sure detect it (see 38586). Testing if the server was started from IDE is not enough. In fact if the same server that IDE is using was started externally the IDE -should- just deploy to it. I do not know any way how to check if the server running at a given port is the one that IDE wants to use.
Hmmmm, so if we should deploy on the same server that IDE is using started externally then the situation is more complicated. IMO we would not have to support this functionality. Anyway, I can imagine a way how to solve this by deploying a special marker webmodule on the IDE server, but it is not worth of the time a possible complications.
Deploying to a server started externally may not be imporant for the bundled server but is probably important for externally added server (e.g. if used by multiple users?). The solution you suggested would probably work if the marker server was deployed when you add the server in IDE, but it would be a bit of hassle and IMO quite error prone. But if you would use ant to deploy it would behave in the same way so I think we do not need to fix this, it is not a bug of netbeans. We do not need to prevent every problem the user may possibly encounter ;-) If reopening please change this to ENHANCEMENT.
I share you opinion that it is a minor problem (as I have already written) which do NOT need to be solved. This issue was intended as a reminder for you rather than a bug.