Petals CDK

The CDK should revert SU state in case of failure of SU deploy, init and start

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • 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, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also PETALSCDK-166).

    It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.

    Show
    According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also PETALSCDK-166). It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:44:07 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:44:16 +0100
Link This issue blocks PETALSCDK-166 [ PETALSCDK-166 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 15:44:22 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:05:13 +0100
Link This issue blocks PETALSESBCONT-404 [ PETALSESBCONT-404 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:08:08 +0100
Link This issue blocks PETALSESBCONT-405 [ PETALSESBCONT-405 ]
Victor NOËL made changes - Mon, 7 Mar 2016 - 16:12:27 +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:27 +0100
Link This issue blocks PETALSDISTRIB-240 [ PETALSDISTRIB-240 ]
Victor NOËL made changes - Tue, 8 Mar 2016 - 15:10:39 +0100
Summary The CDK should revert state in case of failure of deploy, init and start The CDK should revert SU state in case of failure of SU deploy, init and start
Victor NOËL made changes - Tue, 8 Mar 2016 - 15:57:44 +0100
Description According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units instead of throwing an exception (see also PETALSCDK-166 for valid cases). According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units instead of throwing an exception (see also PETALSCDK-166 for valid cases).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.
Victor NOËL made changes - Tue, 22 Mar 2016 - 17:06:23 +0100
Description According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units instead of throwing an exception (see also PETALSCDK-166 for valid cases).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called. 		According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also PETALSCDK-166 for valid cases).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.
Victor NOËL made changes - Tue, 22 Mar 2016 - 17:06:42 +0100
Description According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also PETALSCDK-166 for valid cases).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called. 		According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also PETALSCDK-166).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.

People

Dates

  • Created:
    Mon, 7 Mar 2016 - 15:43:59 +0100
    Updated:
    Tue, 22 Mar 2016 - 17:06:42 +0100
    Resolved:
    Mon, 7 Mar 2016 - 16:12:27 +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.