[jira] Updated: (UIMA-1172) JMX client mbean should have attribute for max and average response latency

["Lev Kozakov (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lev Kozakov updated UIMA-1172:
------------------------------

    Attachment: uima-1172_uimaj-as-jms.patch
                uima-1172_uimaj-as-core.patch

Added 2 timing parameters in the client MBean: TimeWaitingForReply and ResponseLatencyTime. The 1st measures the time interval between sending serialized CAS to the service queue and receiving serialized result from the queue. The 2nd measures the full response latency time per CAS, including the TimeWaitingForReply plus input CAS serialization time and result CAS deserialization time.

Also, made some methods in the client MBean implementation synchronized to support multi-threaded read/write access to the MBean.

> JMX client mbean should have attribute for max and average response latency
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-1172
>                 URL: https://issues.apache.org/jira/browse/UIMA-1172
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>         Attachments: uima-1172_uimaj-as-core.patch, uima-1172_uimaj-as-jms.patch
>
>
> An important performance parameter for a UIMA AS service is 
> the response latency as measured by a client application.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.