[#PETALSANT-9] 'jbi-deploy-service-assembly' does not fail when an error occurs during the deployment - Petals Link JIRA

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 2.4.0
Fix Version/s: 2.5.0
Component/s: Task 'jbi-deploy-service-assembly'
Security Level: Public

Description:

Hide

If the deployment of a service assembly succeeds on the container side, returning a deployment report with errors at service-unit level, the Petals Ant Task jbi-deploy-service-assembly does not fail even if the attribute failOnError is set to true.
Only the error is logged on the Ant task side:

[jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT':
[jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component.
[jbi-deploy-service-assembly] 	at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132)
[jbi-deploy-service-assembly] 	at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169)
...
...
...
[jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure

Show

[jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT':
[jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component.
[jbi-deploy-service-assembly] 	at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132)
[jbi-deploy-service-assembly] 	at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] 	at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169)
...
...
...
[jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure

Environment:

-

Issue Links

Depends

This issue blocks:
PETALSANT-25 Generalization of attribute 'failOnComponentError'

Activity

Ascending order - Click to sort in descending order

Christophe DENEUX made changes - Thu, 26 Mar 2015 - 10:41:19 +0100

Field	Original Value	New Value
Fix Version/s		2.4.1 [ 10521 ]
Priority		Major [ 3 ]
Description	If the deployment of a service assembly fails on the contaider side, returning a deployment report with errors, the Petals Ant Task {{jbi-deploy-service-assembly}} does not fail even if the attribute {{failOnError}} is set to {{true}}. We have only the error logged by the Ant task: {code} [jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT': [jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component. [jbi-deploy-service-assembly] at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132) [jbi-deploy-service-assembly] at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169) ... ... ... [jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure {code}	If the deployment of a service assembly fails on the contaider side, returning a deployment report with errors, the Petals Ant Task {{jbi-deploy-service-assembly}} does not fail even if the attribute {{failOnError}} is set to {{true}}. Only the error is logged on the Ant task side: {code} [jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT': [jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component. [jbi-deploy-service-assembly] at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132) [jbi-deploy-service-assembly] at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73) [jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169) ... ... ... [jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure {code}

Christophe DENEUX made changes - Thu, 26 Mar 2015 - 10:41:25 +0100

Status

New [ 10000 ]

Open [ 10002 ]

Christophe DENEUX made changes - Thu, 26 Mar 2015 - 10:41:28 +0100

Status

Open [ 10002 ]

In Progress [ 10003 ]

Hide

Permalink

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 10:44:54 +0100

An integration test about this problem has been added with svn#37046

Show

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 10:44:54 +0100 An integration test about this problem has been added with svn#37046

Christophe DENEUX made changes - Thu, 26 Mar 2015 - 10:54:35 +0100

Description

If the deployment of a service assembly fails on the contaider side, returning a deployment report with errors, the Petals Ant Task {{jbi-deploy-service-assembly}} does not fail even if the attribute {{failOnError}} is set to {{true}}.
Only the error is logged on the Ant task side:
{code}
[jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT':
[jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component.
[jbi-deploy-service-assembly] at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132)
[jbi-deploy-service-assembly] at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169)
...
...
...
[jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure
{code}

If the deployment of a service assembly *succeeds* on the container side, returning a *deployment report with errors at service-unit level*, the Petals Ant Task {{jbi-deploy-service-assembly}} does not fail even if the attribute {{failOnError}} is set to {{true}}.
Only the error is logged on the Ant task side:
{code}
[jbi-deploy-service-assembly] Failed to deploy SU 'su-xslt-two-provides-5.0.0-SNAPSHOT':
[jbi-deploy-service-assembly] org.ow2.petals.component.framework.api.exception.PEtALSCDKException: Only one 'Provides' section is allowed by this component.
[jbi-deploy-service-assembly] at org.ow2.petals.se.xslt.XsltSuManager.doDeploy(XsltSuManager.java:132)
[jbi-deploy-service-assembly] at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.deploy(AbstractServiceUnitManager.java:266)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.deploySUtoComponent(DeploySUToComponentTask.java:122)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeploySUToComponentTask.execute(DeploySUToComponentTask.java:75)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.registerAndDeploySU(DeployAllSUTask.java:165)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.deploySUS(DeployAllSUTask.java:122)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.task.deployment.deploy.DeployAllSUTask.execute(DeployAllSUTask.java:81)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.api.jbi.management.TaskProcessor.process(TaskProcessor.java:73)
[jbi-deploy-service-assembly] at org.ow2.petals.microkernel.jbi.management.deployment.DeploymentServiceImpl.deploy(DeploymentServiceImpl.java:169)
...
...
...
[jbi-deploy-service-assembly] Service assembly 'sa-xslt-undeployable-su-5.0.0-SNAPSHOT' deployed with some SU deployment in failure
{code}

Hide

Permalink

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 11:57:03 +0100

On the model of DeploymentServiceMBean, we think that the Petals Ant task jbi-deploy-service-assembly:

must fail on an error of the implementation’s execution of the task (ie. the tag frmwk-task-result/frmwk-task-result-details/task-result-details/task-result of the deployment report is FAILED) according to the value of the attribute failOnError,
must not fail on an error of interaction(s) with a component (ie. the tag component-task-result/component-task-result-details/task-result-details/task-result of the deployment report is FAILED) except if a new attribute failOnComponentError is set to true.

The default value of failOnComponentError is false to be aligned on the processing of DeploymentServiceMBean.

When failOnComponentError is set to true, if failOnError is set to false, the Petals Ant task will not fail.

Show

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 11:57:03 +0100 On the model of DeploymentServiceMBean, we think that the Petals Ant task jbi-deploy-service-assembly:

must fail on an error of the implementation’s execution of the task (ie. the tag frmwk-task-result/frmwk-task-result-details/task-result-details/task-result of the deployment report is FAILED) according to the value of the attribute failOnError,
must not fail on an error of interaction(s) with a component (ie. the tag component-task-result/component-task-result-details/task-result-details/task-result of the deployment report is FAILED) except if a new attribute failOnComponentError is set to true.

The default value of failOnComponentError is false to be aligned on the processing of DeploymentServiceMBean. When failOnComponentError is set to true, if failOnError is set to false, the Petals Ant task will not fail.

Hide

Permalink

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 15:55:46 +0100

Fixed in trunk

Show

Christophe DENEUX added a comment - Thu, 26 Mar 2015 - 15:55:46 +0100 Fixed in trunk

Christophe DENEUX made changes - Thu, 26 Mar 2015 - 15:55:46 +0100

Status	In Progress [ 10003 ]	Resolved [ 10004 ]
Resolution		Fixed [ 1 ]

Hide

Permalink

Victor NOËL added a comment - Thu, 26 Mar 2015 - 17:45:21 +0100

I'm not totally happy with the fix: now this task is the ONLY one that throws an exception (and thus failOnError) when something is going wrong.

And actually, if the SA fails to deploy (the last else in the code) no exception is thrown (and thus the failOnError is not used).

The same happens for every task! And the jbi-start-service-assembly task has not the same structure as the deploy even though starting an SU could fail...

I think failOnError was there to fail when an error OTHER than a failing of the actual business task happened.

Anyway, we must fix that in a coherent way or not touch it...

Show

Victor NOËL added a comment - Thu, 26 Mar 2015 - 17:45:21 +0100 I'm not totally happy with the fix: now this task is the ONLY one that throws an exception (and thus failOnError) when something is going wrong. And actually, if the SA fails to deploy (the last else in the code) no exception is thrown (and thus the failOnError is not used). The same happens for every task! And the jbi-start-service-assembly task has not the same structure as the deploy even though starting an SU could fail... I think failOnError was there to fail when an error OTHER than a failing of the actual business task happened. Anyway, we must fix that in a coherent way or not touch it...

Victor NOËL made changes - Thu, 26 Mar 2015 - 17:45:22 +0100

Status	Resolved [ 10004 ]	Open [ 10002 ]
Resolution	Fixed [ 1 ]
Component/s		Task 'jbi-install-component' [ 10343 ]
Component/s		Task 'jbi-install-shared-library' [ 10345 ]
Component/s		Task 'jbi-list-binding-components' [ 10356 ]
Component/s		Task 'jbi-list-service-assemblies' [ 10358 ]
Component/s		Task 'jbi-list-service-engines' [ 10355 ]
Component/s		Task 'jbi-list-shared-libraries' [ 10357 ]
Component/s		Task 'jbi-shut-down-component' [ 10349 ]
Component/s		Task 'jbi-shut-down-service-assembly' [ 10354 ]
Component/s		Task 'jbi-start-component' [ 10347 ]
Component/s		Task 'jbi-start-service-assembly' [ 10352 ]
Component/s		Task 'jbi-stop-component' [ 10348 ]
Component/s		Task 'jbi-stop-service-assembly' [ 10353 ]
Component/s		Task 'jbi-undeploy-service-assembly' [ 10351 ]
Component/s		Task 'jbi-uninstall-component' [ 10344 ]
Component/s		Task 'jbi-uninstall-shared-library' [ 10346 ]

Hide

Permalink

Christophe DENEUX added a comment - Fri, 27 Mar 2015 - 09:19:02 +0100

Yes and no !

You're right when telling that, according to the source code of the Ant task, if the SA fails to deploy (the last else in the code) no exception is throw. But when saying "the SA fails to deploy", you must tell the difference between:

the implementation’s execution of the task DeploymentServiceMBean.deploy(),
and, the interaction(s) with a component during DeploymentServiceMBean.deploy()

Moreover, according to the §6.6 of JBI specifications:

The package must conform to the requirements detailed in the section on “Service Assembly Packaging”, else the deployment MUST fail (by throwing a java.lang.Exception) without attempting to deploy any of the service units contained within the assembly.
...
If all service units of the assembly fail to deploy, a failure exception MUST be thrown. If at least one service unit deployment succeeds, then any failures MUST be reported using the status return String of the DeploymentServiceMBeans’s deploy() method.

I will check the container source code about the possibility to have a deployment report with a status FAILED in the part of the implementation’s execution of the task DeploymentServiceMBean.deploy().

Show

Christophe DENEUX added a comment - Fri, 27 Mar 2015 - 09:19:02 +0100 Yes and no ! You're right when telling that, according to the source code of the Ant task, if the SA fails to deploy (the last else in the code) no exception is throw. But when saying "the SA fails to deploy", you must tell the difference between:

the implementation’s execution of the task DeploymentServiceMBean.deploy(),
and, the interaction(s) with a component during DeploymentServiceMBean.deploy()

Moreover, according to the §6.6 of JBI specifications:

The package must conform to the requirements detailed in the section on “Service Assembly Packaging”, else the deployment MUST fail (by throwing a java.lang.Exception) without attempting to deploy any of the service units contained within the assembly. ... If all service units of the assembly fail to deploy, a failure exception MUST be thrown. If at least one service unit deployment succeeds, then any failures MUST be reported using the status return String of the DeploymentServiceMBeans’s deploy() method.

So, I see no case where we can have a deployment report where the part linked to the implementation’s execution of the task has a status FAILED because an exception is thrown by DeploymentServiceMBean.deploy(). And so, I think that the last statement else in the code is a dead code part. In doubt, I don't remove it. I will check the container source code about the possibility to have a deployment report with a status FAILED in the part of the implementation’s execution of the task DeploymentServiceMBean.deploy().

Hide

Permalink

Christophe DENEUX added a comment - Fri, 27 Mar 2015 - 09:33:10 +0100

According to the container source code (svn#37049) , no deployment report can be generated with a status FAILED in the part of the implementation’s execution of the task DeploymentServiceMBean.deploy().

Show

Christophe DENEUX added a comment - Fri, 27 Mar 2015 - 09:33:10 +0100 According to the container source code (svn#37049) , no deployment report can be generated with a status FAILED in the part of the implementation’s execution of the task DeploymentServiceMBean.deploy().

Hide

Permalink

Victor NOËL added a comment - Fri, 27 Mar 2015 - 11:58:04 +0100

Ok, I better understand, so at least we should maybe generalise the failOnComponentError to other task?

Show

Victor NOËL added a comment - Fri, 27 Mar 2015 - 11:58:04 +0100 Ok, I better understand, so at least we should maybe generalise the failOnComponentError to other task?

Hide

Permalink

Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 10:51:45 +0200 - edited

Generalization will be done through PETALSANT-25

Show

Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 10:51:45 +0200 - edited Generalization will be done through PETALSANT-25

Christophe DENEUX made changes - Mon, 5 Oct 2015 - 10:51:46 +0200

Affects Version/s

2.5.1 [ 10598 ]

Christophe DENEUX made changes - Mon, 5 Oct 2015 - 10:52:49 +0200

Fix Version/s		2.5.1 [ 10598 ]
Affects Version/s	2.5.1 [ 10598 ]

Christophe DENEUX made changes - Mon, 23 May 2016 - 11:55:41 +0200

Fix Version/s		2.6.1 [ 10628 ]
Fix Version/s	2.6.0 [ 10598 ]

Christophe DENEUX made changes - Mon, 12 Sep 2016 - 17:02:45 +0200

Link

This issue blocks PETALSANT-25 [ PETALSANT-25 ]

Christophe DENEUX made changes - Mon, 12 Sep 2016 - 17:03:47 +0200

Component/s	Task 'jbi-install-component' [ 10343 ]
Component/s	Task 'jbi-install-shared-library' [ 10345 ]
Component/s	Task 'jbi-list-binding-components' [ 10356 ]
Component/s	Task 'jbi-list-service-assemblies' [ 10358 ]
Component/s	Task 'jbi-list-service-engines' [ 10355 ]
Component/s	Task 'jbi-list-shared-libraries' [ 10357 ]
Component/s	Task 'jbi-shut-down-component' [ 10349 ]
Component/s	Task 'jbi-shut-down-service-assembly' [ 10354 ]
Component/s	Task 'jbi-start-component' [ 10347 ]
Component/s	Task 'jbi-start-service-assembly' [ 10352 ]
Component/s	Task 'jbi-stop-component' [ 10348 ]
Component/s	Task 'jbi-stop-service-assembly' [ 10353 ]
Component/s	Task 'jbi-undeploy-service-assembly' [ 10351 ]
Component/s	Task 'jbi-uninstall-component' [ 10344 ]
Component/s	Task 'jbi-uninstall-shared-library' [ 10346 ]

Christophe DENEUX made changes - Mon, 12 Sep 2016 - 17:04:37 +0200

Status

Open [ 10002 ]

In Progress [ 10003 ]

Christophe DENEUX made changes - Mon, 12 Sep 2016 - 17:06:25 +0200

Fix Version/s

2.6.1 [ 10628 ]

Christophe DENEUX made changes - Mon, 12 Sep 2016 - 17:06:35 +0200

Status	In Progress [ 10003 ]	Resolved [ 10004 ]
Resolution		Fixed [ 1 ]

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

1m 30s

Christophe DENEUX

Thu, 26 Mar 2015 - 10:41:25 +0100

Open

In Progress

Christophe DENEUX

Thu, 26 Mar 2015 - 10:41:28 +0100

In Progress

Resolved

5h 14m

Christophe DENEUX

Thu, 26 Mar 2015 - 15:55:46 +0100

Resolved

Open

1h 49m

Victor NOËL

Thu, 26 Mar 2015 - 17:45:22 +0100

Open

In Progress

535d 22h 19m

Christophe DENEUX

Mon, 12 Sep 2016 - 17:04:37 +0200

In Progress

Resolved

1m 58s

Christophe DENEUX

Mon, 12 Sep 2016 - 17:06:35 +0200

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 26 Mar 2015 - 10:39:55 +0100

Updated:

Mon, 12 Sep 2016 - 17:06:35 +0200

Resolved:

Mon, 12 Sep 2016 - 17:06:35 +0200

Petals Ant Tasks

'jbi-deploy-service-assembly' does not fail when an error occurs during the deployment

Details

Issue Links

Activity

People

Dates