Petals CDK

SU lifecycle operations should throw exceptions in case of failure

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

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 5.5.0
Fix Version/s: 5.6.0
Component/s: None
Security Level: Public

Description:
Hide
According to the JBI specification, all the operation of the service unit lifecycle should throw exception in the following cases:

the SU is not deployed (except for deploy for which it is when an SU with the same name already exists).

incoherent state (except for deploy again).

Nevertheless, in Petals, we consider that other reasons of failure are better reported through exceptions instead of being logged (it is easier for the container to find them and report them to the admin).
Show
According to the JBI specification, all the operation of the service unit lifecycle should throw exception in the following cases:

the SU is not deployed (except for deploy for which it is when an SU with the same name already exists).

incoherent state (except for deploy again).

Nevertheless, in Petals, we consider that other reasons of failure are better reported through exceptions instead of being logged (it is easier for the container to find them and report them to the admin).

Environment:

-

Issue Links

Depends

This issue depends on:
~~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
~~PETALSESBCONT-405~~ Remove the UNKNOWN state for SAs and SUs

Activity

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Mon, 7 Mar 2016 - 15:43:01 +0100

Updated:

Tue, 22 Mar 2016 - 15:46:36 +0100

Resolved:

Mon, 7 Mar 2016 - 16:12:30 +0100