Petals ESB CLI

Operation query on response time SOAP metrics are broken

Details

  • Description:
    Hide

    Petals CLI command `monitoring ... --query-operations ...` for BC SOAP monitoring on `outgoing-ws-requests-response-times` and `incoming-ws-requests-response-times` are broken, the following error is returned:

    java.lang.IllegalArgumentException: Unknown ws-request execution status value: http://www.w3.org/ns/wsdl/in-out
    at org.ow2.petals.jmx.api.api.monitoring.component.soap.WsRequestExecutionStatus.parse(WsRequestExecutionStatus.java:51)
    at org.ow2.petals.jmx.api.impl.monitoring.component.bc.soap.BcSoapMonitoringServiceClientImpl.getOutgoingWsRequestsResponseTimesGroupedBySvcAndExecStatus(BcSoapMonitoringServiceClientImpl.java:472)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.query(OutgoingWsRequestsResponseTimes.java:426)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.listOperations(OutgoingWsRequestsResponseTimes.java:338)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.execute(OutgoingWsRequestsResponseTimes.java:302)
    at org.ow2.petals.cli.extension.command.monitoring.Monitoring.execute(Monitoring.java:488)
    at org.ow2.petals.cli.shell.AbstractShell.evaluate(AbstractShell.java:365)
    at org.ow2.petals.cli.shell.AbstractShell.evaluate(AbstractShell.java:397)
    at org.ow2.petals.cli.shell.PetalsInteractiveCli.run(PetalsInteractiveCli.java:90)
    at org.ow2.petals.cli.AbstractMain.createAndRunPetalsCLIShell(AbstractMain.java:293)
    at org.ow2.petals.cli.AbstractMain.run(AbstractMain.java:206)
    at org.ow2.petals.cli.Main.main(Main.java:49)
    Show
    Petals CLI command `monitoring ... --query-operations ...` for BC SOAP monitoring on `outgoing-ws-requests-response-times` and `incoming-ws-requests-response-times` are broken, the following error is returned: 
    java.lang.IllegalArgumentException: Unknown ws-request execution status value: http://www.w3.org/ns/wsdl/in-out
    at org.ow2.petals.jmx.api.api.monitoring.component.soap.WsRequestExecutionStatus.parse(WsRequestExecutionStatus.java:51)
    at org.ow2.petals.jmx.api.impl.monitoring.component.bc.soap.BcSoapMonitoringServiceClientImpl.getOutgoingWsRequestsResponseTimesGroupedBySvcAndExecStatus(BcSoapMonitoringServiceClientImpl.java:472)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.query(OutgoingWsRequestsResponseTimes.java:426)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.listOperations(OutgoingWsRequestsResponseTimes.java:338)
    at org.ow2.petals.cli.extension.command.monitoring.mo.components.bc.soap.OutgoingWsRequestsResponseTimes.execute(OutgoingWsRequestsResponseTimes.java:302)
    at org.ow2.petals.cli.extension.command.monitoring.Monitoring.execute(Monitoring.java:488)
    at org.ow2.petals.cli.shell.AbstractShell.evaluate(AbstractShell.java:365)
    at org.ow2.petals.cli.shell.AbstractShell.evaluate(AbstractShell.java:397)
    at org.ow2.petals.cli.shell.PetalsInteractiveCli.run(PetalsInteractiveCli.java:90)
    at org.ow2.petals.cli.AbstractMain.createAndRunPetalsCLIShell(AbstractMain.java:293)
    at org.ow2.petals.cli.AbstractMain.run(AbstractMain.java:206)
    at org.ow2.petals.cli.Main.main(Main.java:49)
  • Environment:
    -

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Pierre Souquet added a comment - Thu, 14 Feb 2019 - 11:34:33 +0100

Fixed in PETALSBCSOAP-216

Show
Pierre Souquet added a comment - Thu, 14 Feb 2019 - 11:34:33 +0100 Fixed in PETALSBCSOAP-216
Hide
Permalink
Pierre Souquet added a comment - Wed, 23 Jan 2019 - 14:12:34 +0100 - edited

The aggregation metrics will not be move to CLI because there is not fine enough raw data in CLI to aggregate properly. To compute response time aggregations it is needed to have all response time measures of the sample. It is not realistic to transfer them through JMX.

Metrics will remain container side and be fixed and improved instead.

Show
Pierre Souquet added a comment - Wed, 23 Jan 2019 - 14:12:34 +0100 - edited The aggregation metrics will not be move to CLI because there is not fine enough raw data in CLI to aggregate properly. To compute response time aggregations it is needed to have all response time measures of the sample. It is not realistic to transfer them through JMX. Metrics will remain container side and be fixed and improved instead.
Hide
Permalink
Christophe DENEUX added a comment - Wed, 23 Jan 2019 - 08:04:59 +0100

This is due to an aggregation method in CDK removing the wrong keys (executionStatus) which is needed in CLI.

As these aggregation metrics will be moved to CLI in PETALSBCSOAP-213, this issue will be resolved as well.

Show
Christophe DENEUX added a comment - Wed, 23 Jan 2019 - 08:04:59 +0100 This is due to an aggregation method in CDK removing the wrong keys (executionStatus) which is needed in CLI. As these aggregation metrics will be moved to CLI in PETALSBCSOAP-213, this issue will be resolved as well.

People

Dates

  • Created:
    Tue, 22 Jan 2019 - 15:17:27 +0100
    Updated:
    Wed, 20 Feb 2019 - 10:44:45 +0100
    Resolved:
    Thu, 14 Feb 2019 - 11:35:46 +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.