Project

General

Profile

Architecture #9820

Stop jetty before upgrading the webapp

Added by Benoît PECCATTE 9 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Target version (plugin):
Effort required:
Tags: Blocking 4.1

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

Related to Rudder - Bug #2807: After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restarted Released 2012-08-14
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 run New

Associated revisions

Revision 27bcd236
Added by Benoît PECCATTE 7 months ago

Fixes #9820: Stop jetty before upgrading the webapp

History

#1 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.0~beta1 to 4.1.0~beta2

#2 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3

#3 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.0~beta3 to 4.1.0~rc1

#4 Updated by François ARMAND 7 months ago

  • Description updated (diff)
  • Assignee set to Benoît PECCATTE

#5 Updated by François ARMAND 7 months ago

  • Tags set to Blocking 4.1

#6 Updated by Benoît PECCATTE 7 months ago

  • Status changed from New to In progress

#7 Updated by Benoît PECCATTE 7 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1273

#8 Updated by Benoît PECCATTE 7 months ago

  • Related to Bug #2807: After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restarted added

#9 Updated by Benoît PECCATTE 7 months ago

  • Status changed from Pending technical review to Pending release

#10 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.0~rc1 which was released today.

#11 Updated by Nicolas CHARLES 6 months ago

  • Related to Bug #10531: When upgrading Rudder to 4.1 on debian8, the web interface is not restarted after properties are modified, so it fails to run added

Also available in: Atom PDF