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

Ascending order - Click to sort in descending order
Pierre Souquet made changes - Tue, 22 Jan 2019 - 15:24:10 +0100
Field Original Value New Value
Link This issue depends on PETALSBCSOAP-213 [ PETALSBCSOAP-213 ]
Christophe DENEUX made changes - Wed, 23 Jan 2019 - 08:04:20 +0100
Priority Critical [ 2 ]
Description Petals CLI commands `--query-operations` for Cacti SOAP monitoring on `outgoing-ws-requests-response-times` and `incoming-ws-requests-response-times` are broken. 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. 		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:
{code}
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)
{code}
Component/s Command 'monitoring' [ 10243 ]
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.
Christophe DENEUX made changes - Wed, 23 Jan 2019 - 08:04:59 +0100
Status New [ 10000 ] Open [ 10002 ]
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.
Pierre Souquet made changes - Thu, 14 Feb 2019 - 11:34:16 +0100
Assignee Christophe DENEUX [ cdeneux ] Pierre Souquet [ psouquet ]
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
Pierre Souquet made changes - Thu, 14 Feb 2019 - 11:35:18 +0100
Link This issue depends on PETALSBCSOAP-216 [ PETALSBCSOAP-216 ]
Pierre Souquet made changes - Thu, 14 Feb 2019 - 11:35:31 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Pierre Souquet made changes - Thu, 14 Feb 2019 - 11:35:46 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 3.1.2 - Petals CLI [ 10914 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Wed, 20 Feb 2019 - 10:44:45 +0100
Fix Version/s 2.1.1 - Extension 'Monitoring' [ 10915 ]
Fix Version/s 3.1.2 - Petals CLI [ 10914 ]
Affects Version/s 2.0.0 - Extension 'Monitoring' [ 10712 ]
Affects Version/s 3.0.0 - Petals CLI [ 10675 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
16h 47m
1
Christophe DENEUX
Wed, 23 Jan 2019 - 08:04:59 +0100
Open Open In Progress In Progress
22d 3h 30m
1
Pierre Souquet
Thu, 14 Feb 2019 - 11:35:31 +0100
In Progress In Progress Resolved Resolved
15s
1
Pierre Souquet
Thu, 14 Feb 2019 - 11:35:46 +0100

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.