Tomcat 9 won't start in 45 seconds, increase time

[AhFai Chan]

Ha, I knew there has to be a Tomcat forum here!

I am running Tomcat 9 on Windows 10 as a virtual server for my Spring WebMvc stuff and lately it won't start, neither automatically in Eclipse as server nor manually, always with the error message that it won't start in 45 seconds and to increase the startup time. So, I increased the startup time to 90 seconds, removed all the hooks to projects in Tomcat, cleaned the catalina directory except for last 2 days and closed all projects except the project I am working on.

Tomcat9 still won't start with the same message to increase the startup time.

Help please? What can I do to get Tomcat to wake up, short of re-installing it ?

[Tim Holloway]

Yep, and you've caught me at one of my oldest homes on the Ranch!

I'm not sure how you've got Eclipse automatically starting Tomcat. I only know how to get it to run Tomcat manually.

Usually under Windows you'd install Tomcat using the Windows installer version which sets it to run as a Windows Service.

Unless you have a serious RAM shortage or some other problem with your system, Tomcat itself should start in under 10 seconds. What takes longer is for the webapps to deploy and start, and I've worked with some that took over 20 minutes to start. So you might want to look for things like long-running init() methods in servlets.

[AhFai Chan]

OK, I think I have resolved the problem
I deleted .m2 folder and Maven rebuilt it.  After that, the project runs.
There are so many projects in there, I must find a common set of .jars with compatible versions and stick to them, I think Maven might have been confused with conflicting versions.

Informed opinion most welcome.

[Tim Holloway]

Maven doesn't have problems with jar versions. Each jar version is stored in a separate subdirectory under .m2. But it never hurts to clean house occastionally, to avoid filling up your disk with "dead" jar versions. You might want to just delete what's in the repositories subdirectory, though, since the main Maven config file is in the actual .m2 directory.