Apache cannot be restarted without an outofmemory error, when .WAR is loaded. Restarting the Apache service without stopping Servoy hangs the restart with an OutOfMemoryError: Java heap space, and a LifecycleExpception: A child container failed during stop.
Does Servoy need to be stopped and started from within Apache Manager or is this a memory issue?
Stopping Servoy and restarting Apache does work, but the restart of Apache should be sufficient.
If memory is the issue, how are memory settings adjusted within Servoy? Attempted to use setenv.bat for main Apache startup; it doesn’t seem to take. The error indicates the container doesn’t have enough memory. There is no restart under servoy-admin, only ‘Enter Maintenance Mode.’ Likely because it is run as a container under Apache, but wanted to see how the actual production use is practiced.
A container restart (so keeping tomcat running) is always a bit tricky there are stuff (depending on how you deploy and what you use) that keeps hanging around
We try to keep cleaning it as much as possible
But i am not sure what you are really doing, just restarting tomcat as a whole shouldn’t result in out of memory, that should just be a kill and a completely fresh start
I don’t see the different between “stopping servoy” (i guess that is stopping the context right) and then restarting tomcat is any different then just restarting tomcat, because the first thing tomcat does is stopping the different context (so what you do by hand is done automatically)