Petals ESB Container

Ensure endpoint registry coherence during recovery

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Resolved
Priority: 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

This issue depends on:
~~PETALSESBCONT-417~~ During container shutdown, keep endpoints in registry and container in topology

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

1m 38s

1

Victor NOËL

Wed, 18 May 2016 - 14:12:03 +0200

Open

In Progress

6d 1h 2m

1

Victor NOËL

Tue, 24 May 2016 - 15:14:21 +0200

In Progress

Resolved

52m 19s

1

Victor NOËL

Tue, 24 May 2016 - 16:06:40 +0200

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

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