Project

General

Profile

Actions

Architecture #9820

closed

Stop jetty before upgrading the webapp

Architecture #9820: Stop jetty before upgrading the webapp

Added by Benoît PECCATTE over 9 years ago. Updated about 9 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 CLARKEActions
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

Updated by Vincent MEMBRÉ about 9 years ago Actions #1

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

Updated by Vincent MEMBRÉ about 9 years ago Actions #2

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

Updated by Vincent MEMBRÉ about 9 years ago Actions #3

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

Updated by François ARMAND about 9 years ago Actions #4

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

Updated by François ARMAND about 9 years ago Actions #5

  • Translation missing: en.field_tag_list set to Blocking 4.1

Updated by Benoît PECCATTE about 9 years ago Actions #6

  • Status changed from New to In progress

Updated by Benoît PECCATTE about 9 years ago Actions #7

  • 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

Updated by Benoît PECCATTE about 9 years ago Actions #8

  • 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

Updated by Benoît PECCATTE about 9 years ago Actions #9

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ about 9 years ago Actions #10

  • Status changed from Pending release to Released

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

Updated by Nicolas CHARLES about 9 years ago Actions #11

  • 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
Actions

Also available in: PDF Atom