Petals ESB CLI

A severe error is loggued on the container side when deploying a service assembly

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.1.0
  • Fix Version/s: 2.1.1
  • Component/s: Command 'deploy'
  • Security Level: Public
  • Description:
    Hide

    When deploying a service assembly that is not already deployed, the following trace is loggued on the container side, and the deployment succeeds:

    0 2013/03/20 13:59:39,218 GMT+0100 SEVERE [Petals.JBI-Management.DeploymentService] : Cannot retrieve service assembly with the specified name : charge-sa-soap-diff-agreg-consume-1.0.0-SNAPSHOT
0 2013/03/20 13:59:39,271 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'charge-su-soap-diff-agreg-consume-1.0.0-SNAPSHOT'
0 2013/03/20 13:59:39,283 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Service Unit 'charge-su-soap-diff-agreg-consume-1.0.0-SNAPSHOT' deployed
    Show
    When deploying a service assembly that is not already deployed, the following trace is loggued on the container side, and the deployment succeeds: 
    0 2013/03/20 13:59:39,218 GMT+0100 SEVERE [Petals.JBI-Management.DeploymentService] : Cannot retrieve service assembly with the specified name : charge-sa-soap-diff-agreg-consume-1.0.0-SNAPSHOT
0 2013/03/20 13:59:39,271 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Deploy Service Unit 'charge-su-soap-diff-agreg-consume-1.0.0-SNAPSHOT'
0 2013/03/20 13:59:39,283 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Service Unit 'charge-su-soap-diff-agreg-consume-1.0.0-SNAPSHOT' deployed
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Wed, 20 Mar 2013 - 14:21:24 +0100

When deploying a service assembly with Petals CLI, a check about the state of the service assembly is done:

  • if the service assembly is shutdown, it will be automaticaly undeploy,
  • if the service assembly is in another state, an error occurs,
  • otherwise, the deployment is launched.

The trace is loggued by the DeploymentService of the Petals container. This trace has not to be printed before to throw the exception.

An issue about the trace in the Petals container has been created: PETALSESBCONT-241

Show
Christophe DENEUX added a comment - Wed, 20 Mar 2013 - 14:21:24 +0100 When deploying a service assembly with Petals CLI, a check about the state of the service assembly is done:
  • if the service assembly is shutdown, it will be automaticaly undeploy,
  • if the service assembly is in another state, an error occurs,
  • otherwise, the deployment is launched.
The trace is loggued by the DeploymentService of the Petals container. This trace has not to be printed before to throw the exception. An issue about the trace in the Petals container has been created: PETALSESBCONT-241
Hide
Permalink
Christophe DENEUX added a comment - Wed, 20 Mar 2013 - 14:39:17 +0100

Fixed by PETALSESBCONT-241

Show
Christophe DENEUX added a comment - Wed, 20 Mar 2013 - 14:39:17 +0100 Fixed by PETALSESBCONT-241

People

Dates

  • Created:
    Wed, 20 Mar 2013 - 14:05:22 +0100
    Updated:
    Wed, 20 Mar 2013 - 14:40:57 +0100
    Resolved:
    Wed, 20 Mar 2013 - 14:39:17 +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.