Eclipse thinks tomcat hasn't started and kills it -
05-21-2009, 08:57 AM
I'm trying to run Tomcat 5.5 within Eclipse 3.4.2 with WTP but it isn't working. I start tomcat, everything seems fine, it's running, I can access web apps in my Web browser, but Eclipse still says "Starting up tomcat..." and then after a while it says "Couldn't start server in 45 seconds" and the server is dead. So somehow it is checking to see if the server is alive, which it is, but Eclipse can't tell that for some reason, and then (I'm guessing a bit here) it kills the server process. I'm on Ubuntu 8.10.
Anyone have any suggestions? Solutions are great, but even someone has some idea how Eclipse establishes the status of the server (in this case incorrectly) that might be helpful. Thanks!
Well, it's entirely possible it's just taking too long to start up. Eclipse has a "time limit", after which it assumes the server isn't going to start. You can increase this timeout in the "Server" tab of Eclipse preferences. From what you describe, this may be a different problem, but it's worth a try.
Thanks for the suggestion, but I don't think that is it, because after a few seconds (but before eclipse tells me tomcat couldn't start up) the console says that tomcat is started and the applications load in my web browser. I've tried increasing the time, that makes it take longer until eclipse kills the server but it still kills it whenever the time is up.