Petals BC REST

Unable to configure port of the embedded HTTP server with Petals CLI

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0.1-BC
  • Fix Version/s: 1.1.0-BC
  • Component/s: Consumer mode
  • Security Level: Public
  • Description:
    Hide

    According to the Petals BC Rest documentation, we should be able to configure the TCP port on which the HTTP server listens incoming REST requests.
    No attribute is available to configure it at installation time using Petals CLI:

    >petals-cli@localhost:7700>deploy -u mvn:org.ow2.petals/petals-bc-rest/1.1.0-SNAPSHOT/zip -D port=8099
AVERTISSEMENT: The component installer is already loaded and only loaded, it has been automatically unloaded.
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: The parameter 'port' does not exist or is not settable for this component

    It seems that the configuration MBean of the component does not contain attribute associated to this parameter.

    Show
    According to the Petals BC Rest documentation, we should be able to configure the TCP port on which the HTTP server listens incoming REST requests. No attribute is available to configure it at installation time using Petals CLI: 
    >petals-cli@localhost:7700>deploy -u mvn:org.ow2.petals/petals-bc-rest/1.1.0-SNAPSHOT/zip -D port=8099
AVERTISSEMENT: The component installer is already loaded and only loaded, it has been automatically unloaded.
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: The parameter 'port' does not exist or is not settable for this component
    It seems that the configuration MBean of the component does not contain attribute associated to this parameter.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 17 Feb 2017 - 17:49:31 +0100 - edited

Yes, no dedicated attribute is available at the configuration MBean level of the component for this parameter.

Waiting to add the right attribute, the only way to configure the component is to update the component JBI descriptor in the component archive.

Show
Christophe DENEUX added a comment - Fri, 17 Feb 2017 - 17:49:31 +0100 - edited Yes, no dedicated attribute is available at the configuration MBean level of the component for this parameter. Waiting to add the right attribute, the only way to configure the component is to update the component JBI descriptor in the component archive.
Christophe DENEUX made changes - Fri, 17 Feb 2017 - 17:49:32 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Critical [ 2 ]
Christophe DENEUX made changes - Fri, 17 Feb 2017 - 17:49:42 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Fri, 17 Feb 2017 - 18:05:41 +0100

Fixed in trunk

Show
Christophe DENEUX added a comment - Fri, 17 Feb 2017 - 18:05:41 +0100 Fixed in trunk
Christophe DENEUX made changes - Fri, 17 Feb 2017 - 18:05:41 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.1.0-BC [ 10696 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
2m
1
Christophe DENEUX
Fri, 17 Feb 2017 - 17:49:32 +0100
Open Open In Progress In Progress
10s
1
Christophe DENEUX
Fri, 17 Feb 2017 - 17:49:42 +0100
In Progress In Progress Resolved Resolved
15m 59s
1
Christophe DENEUX
Fri, 17 Feb 2017 - 18:05:41 +0100



People

Dates

  • Created:
    Fri, 17 Feb 2017 - 17:47:32 +0100
    Updated:
    Fri, 17 Feb 2017 - 18:05:41 +0100
    Resolved:
    Fri, 17 Feb 2017 - 18:05:41 +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.