Ticket #3573 (closed defect: Fixed)

Opened 5 months ago

Last modified 4 months ago

ZenJMX does not use parameter values when performing operation calls

Reported by: jplouis Owned by: jplouis
Priority: 1 - Blocker Milestone: zenoss-2.3
Component: ZenJMX Version: 2.2.3
Keywords: zenoss-2.2.4-verified Cc:
Community Patch Attached: Deployed @ Customer:
Installer: Maintenance Target:
Specific ZenPack: Maintenance Status:
Documentation Note?: Not required Regression:

Description

the "paramater values" and "parameter types" are not used by zenjmx for operation invokes on mbeans

Change History

Changed 5 months ago by jplouis

  • owner changed from edahl to jplouis

Changed 5 months ago by jplouis

  • status changed from new to closed
  • resolution set to fixed

(In [9876]) fixes #3573 fix OperationCall to use parameter values when making jmx invoke calls

Changed 5 months ago by bbibeault

  • keywords zenoss-2.2.4-accepted added; zenoss-2.2.4-proposed removed
  • reviewed changed from 0 to 1

Changed 5 months ago by bbibeault

  • priority changed from high to blocker

Changed 5 months ago by ian

(In [9985]) Refs #3573: Backporting r9876 to the zenoss-2.2.x branch

Changed 5 months ago by ian

  • keywords zenoss-2.2.4-patched added; zenoss-2.2.4-accepted removed

Changed 4 months ago by jplouis

  • component changed from All to ZenJMX

Changed 4 months ago by bedwards

  • keywords zenoss-2.2.4-verified added; zenoss-2.2.4-patched removed

Steps to verify in 2.2.4:

  • create remote jmx server with an operation that takes a parameter and run it
  • discover my mac as a device. classify it as /Server/Darwin
  • add ZenJMX as a Template for the device (tricky multi-select should be fixed)
  • add datasource, datapoint, and graph for my parameterized operation
  • zenjmx restart
  • wait a few minutes for the perf graphs to update
Note: See TracTickets for help on using tickets.