Accepted answer

open the servers view -> double click tomcat -> drop down the timeouts section

there you can increase the startup time for each particular server.


i have tomcat 8 update 25 and tomcat 7 but facing the same issue it shows the message server tomcat v7.0 server at localhost was unable to start within 45 seconds. if the server requires more time, try increasing the timeout in the server editor.


this problem can occur if you have altogether too much stuff being started when the server is started -- or if you are in debug mode and stepping through the initialization sequence. in eclipse, changing the start-timeout by 'opening' the tomcat server entry 'servers view' tab of the debug perspective is convenient. in some situations it is useful to know where this setting is 'really' stored.

tomcat reads this setting from the element in the element in the servers.xml file. this file is stored in the .metatdata/.plugins/org.eclipse.wst.server.core directory of your eclipse workspace, ie:


there are other juicy configuration files for eclipse plugins in other directories under .metadata/.plugins as well.

here's an example of the servers.xml file, which is what is changed when you edit the tomcat server configuration through the eclipse gui:

note the 'start-timeout' property that is set to a good long 1200 seconds above.


i also had the issue of the eclipse tomcat server timing out and tried every suggestion including:

  • increasing timeout seconds
  • deleting various .metadata files in workspace directory
  • deleting the server instance in eclipse along with the run config

nothing worked until i read rohitdev's comment and realized that i had, in fact added a breakpoint in an interceptor class after a big code change and had forgotten to toggle it off. i removed it and all other breakpoints and tomcat started right up.



server timeout can be specified there.

or another method via the servers tab here:


the issue is also created if you have setup breakpoints in the code and trying to start tomcat in debug mode post some code overhaul.

solution is to clear all the breakpoints.


double click tomcat , see configure setting with "timeout" modify the number. maybe this not the tomcat error.u can see the db connection is achievable.


double click on server and see the timeouts section and add more time look at the picture enter image description here


solved: that's it!!!! for me was compiling with jdk6 but running tomcat with jdk7, wst uses the system properties and not the eclipse settings. i also configure the same jdk version in eclipse and in system (check it with java -version in cmd line)

details: i try to configure eclipse like describe here, but it didn´t solve the problem, then i notice in eclipse´s error log that tomcat was started with jre 1.7. in spite of my configurations.

i also try, in cmd line, 'java -version' and obtained '1.7' instead of expected '1.6'.

i also decide to configure java 1.6 (like in eclipse) in system panel but it didn´t solve the problem. i also desinstall jre 1.7 restart eclipse and it success!.. it was a very usefull clue, thank you.


  1. go to server view
  2. double click the server for which you want to change the time limit
  3. on the right hand side you have timeouts dropdown tab. select that.
  4. you then have option to change the time limits.

enter image description here

Related Query

More Query from same tag