Petals CDK

SU lifecycle operations should throw exceptions in case of failure

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor 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

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:43:10 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Minor [ 4 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:43:12 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:44:16 +0100
Link This issue depends on PETALSCDK-167 [ PETALSCDK-167 ]
Hide
Permalink
Victor NOËL added a comment - Mon, 7 Mar 2016 - 15:52:02 +0100

Add explanation for the need of an exception in deploy.

Show
Victor NOËL added a comment - Mon, 7 Mar 2016 - 15:52:02 +0100 Add explanation for the need of an exception in deploy.
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:52:02 +0100
Description 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 of course).
 - incoherent state (except for deploy again).

It is not totally clear what is the purpose of the exception for deploy since the result must only be returned through the status String. 		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).
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:08:16 +0100
Link This issue blocks PETALSESBCONT-405 [ PETALSESBCONT-405 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:12:30 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.6.0 [ 10611 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Mon, 7 Mar 2016 - 16:15:40 +0100
Link This issue blocks PETALSDISTRIB-240 [ PETALSDISTRIB-240 ]
Hide
Permalink
Victor NOËL added a comment - Tue, 22 Mar 2016 - 15:46:35 +0100

updated the description/title.

Show
Victor NOËL added a comment - Tue, 22 Mar 2016 - 15:46:35 +0100 updated the description/title.
Victor NOËL made changes - Tue, 22 Mar 2016 - 15:46:36 +0100
Summary Failure of SU lifecycle operations should only throw exceptions in case of incoherent state SU lifecycle operations should throw exceptions in case of failure
Description 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). 		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).
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
9s
1
Victor NOËL
Mon, 7 Mar 2016 - 15:43:10 +0100
Open Open In Progress In Progress
2s
1
Victor NOËL
Mon, 7 Mar 2016 - 15:43:12 +0100
In Progress In Progress Resolved Resolved
29m 18s
1
Victor NOËL
Mon, 7 Mar 2016 - 16:12:30 +0100



People

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
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.