Question:
Why many time after launching the Tomcat service, it takes so much time to go to the OpenmMRS webapp? Going to the webpage index or tomcat manager is very slow more then several minutes, I have already installed all the plugins and I don’t think it has to rebuild the index at each start.
Can you please help me on how to figure this out ?
It typically takes several minutes to start the OpenMRS webapp in tomcat
(with all the Reference Application modules included).
If you are watching the tomcat log file, the steps that are slowest
willlook something like these:
INFO - ServiceContext.startRefreshingContext(902) |2016-02-01 11:40:48,116| Refreshing Context
INFO - LocalSessionFactoryBean.buildSessionFactory(780) |2016-02-01 11:40:59,933| Building new Hibernate SessionFactory
How long does this actually take to load for you? If it’s taken >5 or >10
minutes (depending on your machine), that would be longer than I expect.
(Also, make sure you have given enough memory to tomcat, per
https://wiki.openmrs.org/x/gxAz)
Or are you saying that every page load takes multiple minutes? That would
be unexpected.
No every single page , but the staring point the first launch of the webapp after Tomcat has been restarded
and regarding this value (-Xmx512m -Xms512m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:NewSize=128m), can I Upgrade them like from 256m to 512m from 512m to 1024m ??
has anyone resolved this issue. When tomcat started with openmrs it is stucked at refreshing context steps >30min . from code it seems it is refreshing spring context for service calls. Not sure which service call call refersh is causing so much time. without logs .it is difficult to track down root cause.
INFO - ServiceContext.startRefreshingContext(883) |2016-04-30 12:16:59,960| Refreshing Context
already huge amount of work is done based on this version and updating will need lots of efforts and testing. to avoid that we are stick to this version. is there any patch for this particular issue that can be applied to reduce timeline while refreshing context…
i am getting a similar problem, after adding modules and restarting tomcat, it takes too long to start. I installed core 2.07. Here are the logs https://pastebin.com/k9B3FEpu
if you happened to have included a custom module, that could be the issue, platform 2.x in my experience has improved start time compared to 1.x. One cause could be you have called a service class at your class level