Project

General

Profile

Actions

Architecture #9820

closed

Stop jetty before upgrading the webapp

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

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Effort required:

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 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 #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Actions #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Actions #4

Updated by François ARMAND about 4 years ago

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

Updated by François ARMAND about 4 years ago

  • Tags set to Blocking 4.1
Actions #6

Updated by Benoît PECCATTE about 4 years ago

  • Status changed from New to In progress
Actions #7

Updated by Benoît PECCATTE about 4 years 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
Actions #8

Updated by Benoît PECCATTE about 4 years 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
Actions #9

Updated by Benoît PECCATTE about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from Pending release to Released

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

Actions #11

Updated by Nicolas CHARLES about 4 years 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
Actions

Also available in: Atom PDF