I was hoping to get some advice on slow startup time for my application after deploying to Tomcat. We are on Hippo 11.2 It appears that there is a wait of up to 5 mins after Tomcat says the application has been deployed before the site application actually responds. The interesting thing is that the ping servlet actually responds that the repository is up and available long before. We are already running repository journal maintenance, which I know affects startup times. Any thoughts?
Hi,
5 minutes is a bit long to start up, but not unusually so IMO. It depends on database size, index checker, repository checker, bootstrapping etc.
The PingServlet indeed shows the behavior described. Since 11.2.8 we also have the PingFilter, which does a better job, see [1]
HTH
Jeroen
[1] https://documentation.bloomreach.com/11/library/administration/pingfilter.html
Would reducing the number of items stored in the bootstrap potentially reduce the startup time? We have a lot of bootstrapped content folders which are probably unnecessary. The database is fairly big (but not unreasonably so) but that’s not something we can tweak.
Hi,
I’m not expecting that removing content folders from bootstrap will increase startup times much. To be sure, you can follow the bootstrapping process by setting log level to INFO or DEBUG of package org.onehippo.repository.bootstrap and/or org.hippoecm.repository.LocalHippoRepository.
Jeroen