Petals ESB Container

Ensure endpoint registry coherence during recovery

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.1
  • Fix Version/s: 5.0.2
  • Component/s: Recovery, Registry
  • Security Level: Public
  • Description:
    Hide

    Currently, during recovery, endpoints are re-activated and replace endpoints that were left (see PETALSESBCONT-417) in the previous execution of the container.

    But if for some reasons some of the previously activated endpoints of the container are not re-activated during recovery, they should not be left as activated since it is 100% sure at that point that they won't be activated automatically anymore and that the only reasons that are activated again is by an administrative action.

    Show
    Currently, during recovery, endpoints are re-activated and replace endpoints that were left (see PETALSESBCONT-417) in the previous execution of the container. But if for some reasons some of the previously activated endpoints of the container are not re-activated during recovery, they should not be left as activated since it is 100% sure at that point that they won't be activated automatically anymore and that the only reasons that are activated again is by an administrative action.
  • Environment:
    -

Issue Links

Depends
 

Activity

People

Dates

  • Created:
    Wed, 18 May 2016 - 14:10:25 +0200
    Updated:
    Tue, 24 May 2016 - 16:06:40 +0200
    Resolved:
    Tue, 24 May 2016 - 16:06:39 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.