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.
because tomcat plugin is checking server status the solution is to cache the value, it has several issues though: - how to 'refresh' the status it the server is started/stopped externally (can be ignored?) - what should be the inital status (either assume it's not running or check the first time)
cannot cache the value until the problem with instantiation will be resolved (currently j2eeserver creates new instances of StartTomcat and calls isRunning on them while another instance of StartTomcat is starting the server)
Could the Tomcat plugin use java.lang.Process.exitValue() to check whether the server is still running?
It could be used now when we always start the server from IDE and have the process descriptor, but the j2eeserver lifecycle document counts with an option that the server could be started externally before the IDE starts and then it would be left running when the IDE exits (which is good esp. for external servers) so we won't have the pd then.
To Petr: Do you mean to start the server with 'catalina.sh run' rather than 'catalina.sh start'? Yes, that's possible. Of course server started outside of IDE is a problem and requires to have some other way how to ping the server anyway. P4 is not accurate IMO
Currently the server is started using 'catalina.sh run'. I made this change in order to implement the redirection of Tomcat stdout and stderr to the IDE output window.
Start/Stop.. action solves the problem.
VERIFIED