Project

General

Profile

Actions

Architecture #9820

closed

Stop jetty before upgrading the webapp

Added by Benoît PECCATTE over 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Effort required:
Name check:
Fix check:
Regression:

Description

When we upgrade the rudder webapp, we let jetty running during the upgrade.
This could lead to subtle bugs.

A better approach would be to stop jetty pre-upgrade and start it post-upgrade.

In all case, Jetty MUST be AT LEAST restarted when the war change, else it WILL lead to problems.


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #2807: After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restartedReleasedJonathan CLARKE2012-08-14Actions
Related to Rudder - Bug #10531: When upgrading Rudder to 4.1 on debian8, the web interface is not restarted after properties are modified, so it fails to runRejectedActions
Actions

Also available in: Atom PDF