Issue: http://issues.qcadoo.org/browse/QCADOO-69
How it works now
The dieing process lunches the restart.shIn this time two instances of tomcat run on the same resources
After the old process died the new one should be upThis is highly OS dependent and can cause race conditions and configurations dependent process behaviour.
...
Issue: http://issues.qcadoo.org/browse/QCADOOMES-117
We should retest with Tomcat 7. It is tolled that it solves many memory leak problems. Plus it has a very nice feature called Parallel Deployments which could use as a fall-back mechanism when some one creates a wrong plugin. We should test how multiple deployments of qcadoo MES affect memory usage.
Useful links:
- http://www.javacodegeeks.com/2011/06/zero-downtime-deployment-and-rollback.html
- http://java.dzone.com/articles/memory-leak-protection-tomcat
- http://www.mkyong.com/tomcat/tomcat-javalangoutofmemoryerror-permgen-space/
- https://blog.coremedia.com/cm/post/1856228/Fight_Tomcats_OutOfMemoryError_PermGen.html
The best way to test this would be to install a clean Tomcat 7 and deploy mes-application*.war (you can find it in qcadoo-src/mes/mes-application/target in a the build sources).
You will however need to:
- copy the qcadoo directory with properties files from the binary distribution to Tomcats 7 distribution
- copy some QCADOO* environmental variables from qcadoo's bin/setenv.sh (or bat) to Tomcats 7 setenv.sh (or bat).
- supply the postgres driver to Tomcats lib directory.
Monitor process
Alternate solution to be considered if the previous fails.
Create a process which monitors the tomcat process. When a restart is requested the monitor firstly shuts down one process and then starts the new one.
...
- mes-application - in this catalog we put all the files that ware in the old binary distribution
- qcadoo-monitor - here we create a minimal tomcat distribution the monitoring web application
Workflow
...
Analysis
| Child pages (Children Display) |
|---|