Petals ESB Container

Remove the UNKNOWN state for SAs and SUs

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

Details

Type: Task
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 5.0.0
Fix Version/s: 5.0.1
Component/s: Administration, Installation/Deployment
Security Level: Public

Description:

Hide

According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs.

The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see ~~PETALSCDK-167~~), nevertheless, it is possible for the SU to throw an exception, but we consider the state is properly handled in that case (see ~~PETALSCDK-166~~).

Show
According to the JBI specification, there is no UNKNOWN state for the SAs and the SUs. The reason is that it is the responsibility of the component to handle failures of lifecycle for the SUs (see ~~PETALSCDK-167~~), nevertheless, it is possible for the SU to throw an exception, but we consider the state is properly handled in that case (see ~~PETALSCDK-166~~).

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSCDK-166~~ SU lifecycle operations should throw exceptions in case of failure
~~PETALSCDK-167~~ The CDK should revert SU state in case of failure of SU deploy, init and start

This issue blocks:
~~PETALSDISTRIB-240~~ Rework Component/SA/SU lifecycle against error situations

Activity

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Mon, 7 Mar 2016 - 16:07:39 +0100

Updated:

Tue, 22 Mar 2016 - 17:08:59 +0100

Resolved:

Tue, 22 Mar 2016 - 17:08:59 +0100