Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

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.

Concepts

WAR redeployment

Just redeploying the WAR application on Tomcat. This would be an ideal solution but was previously tested i shown the following faults:

  • Tomcat generally crushes after 3-6 hot redeploys
    • this may be due to some configuration options
    • exploded WAR's have many problems, maybe configuring Tomcat to not explode the WAR is an solution
  • qcadoo MES may have memory leaks on startup and shutdown
  • by default garbage collection does not sweep old unused class bitcode

Issue: http://issues.qcadoo.org/browse/QCADOOMES-117

Monitor process

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.

  • No labels