JAX-WS monitoring

We can use the endpoint MXBean for JAX-WS monitoring of Liberty.

Performance data is available for each endpoint and operation in the JAX-WS application. Each web service endpoint has its own MXBean.

The ObjectName for identifying each endpoint MXBean might be in one of the following formats: 

    org.apache.cxf:bus.id=<bus.name>,type=Performance.Counter.Server,service="<NameSpace><ServiceName>",port="<PortName>"
org.apache.cxf:bus.id=<bus.name>,type=Performance.Counter.Client,service="<NameSpace><ServiceName>",port="<PortName>"

For example: 

    org.apache.cxf:bus.id=JaxWsLibertyDemo-Server-Bus,type=Performance.Counter.Server,
    service="{http://jaxws.samples/}SimpleEchoService",port="SimpleEchoPort"
org.apache.cxf:bus.id=JaxWsLibertyDemo-Server-Bus,type=Performance.Counter.Client,
    service="{http://jaxws.samples/}SimpleEchoService",port="SimpleEchoPort"

This MXBean is responsible for reporting the web service status of each endpoint and operation.

    Counter definitions (Attributes to MXBean)

      AvgResponseTime Average response time (millisecond).
      MaxResponseTime Maximum response time (millisecond).
      MinResponseTime Minimum response time (millisecond).
      NumInvocations Number of invocations to this endpoint or operation.
      NumChekedApplicationFaults Number of checked application faults.
      NumLogicalRuntimFaluts Number of logical runtime faults.
      NumRuntimeFaults Number of runtime faults.
      NumUnCheckedApplicationFaults Number of unchecked application faults.
      TotalHandlingTime Total response handling time (millisecond)..

    Management Interface

    The management interface for web service application monitoring is...

    We can use the management interface to obtain a proxy object.

    See Examples of accessing MBean attributes and operations.


Parent topic: Monitoring with monitor-1.0