Petals CDK

The CDK should revert component state in case of failure of component 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

    The JBI specification is not so clear about that, but it is relevant to think it is the responsibility of the component to take care its own state in case of failure of init and start.

    So, mirroring the behaviour of the CDK in PETALSCDK-167, if the execution of doInit or doStart fails, then the opposite operation doShutdown or doStop will be called.

    In opposition with PETALSCDK-166, these methods should still thrown an exception and the component will be put in state UNKNOWN.

    Show
    The JBI specification is not so clear about that, but it is relevant to think it is the responsibility of the component to take care its own state in case of failure of init and start. So, mirroring the behaviour of the CDK in PETALSCDK-167, if the execution of doInit or doStart fails, then the opposite operation doShutdown or doStop will be called. In opposition with PETALSCDK-166, these methods should still thrown an exception and the component will be put in state UNKNOWN.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Tue, 8 Mar 2016 - 15:13:15 +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 - Tue, 8 Mar 2016 - 15:13:17 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Tue, 8 Mar 2016 - 16:01:58 +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 init and start. The JBI specification is not so clear about that, but it is relevant to think it is the responsibility of the component to take care its own state in case of failure of init and start.

So, mirroring the behaviour of the CDK in PETALSCDK-167, if the execution of doInit or doStart fails, then the opposite operation doShutdown or doStop will be called.
Victor NOËL made changes - Tue, 8 Mar 2016 - 16:16:34 +0100
Link This issue blocks PETALSDISTRIB-240 [ PETALSDISTRIB-240 ]
Victor NOËL made changes - Tue, 8 Mar 2016 - 16:53:01 +0100
Description The JBI specification is not so clear about that, but it is relevant to think it is the responsibility of the component to take care its own state in case of failure of init and start.

So, mirroring the behaviour of the CDK in PETALSCDK-167, if the execution of doInit or doStart fails, then the opposite operation doShutdown or doStop will be called. 		The JBI specification is not so clear about that, but it is relevant to think it is the responsibility of the component to take care its own state in case of failure of init and start.

So, mirroring the behaviour of the CDK in PETALSCDK-167, if the execution of doInit or doStart fails, then the opposite operation doShutdown or doStop will be called.

In opposition with PETALSCDK-166, these methods should still thrown an exception and the component will be put in state UNKNOWN.
Victor NOËL made changes - Tue, 8 Mar 2016 - 17:11:32 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.6.0 [ 10611 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Tue, 8 Mar 2016 - 15:13:02 +0100
    Updated:
    Tue, 8 Mar 2016 - 17:11:31 +0100
    Resolved:
    Tue, 8 Mar 2016 - 17:11:31 +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.