[jira] [Resolved] (UIMA-3519) JMS service stub causes broker problems at high load

["Eddie Epstein (JIRA)" <de...@uima.apache.org>]

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

Eddie Epstein resolved UIMA-3519.
---------------------------------
    Resolution: Fixed

> JMS service stub causes broker problems at high load
> ----------------------------------------------------
>
>                 Key: UIMA-3519
>                 URL: https://issues.apache.org/jira/browse/UIMA-3519
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>            Assignee: Eddie Epstein
>
> Scenario:
> A UIMA aggregate includes a JMS remote service, the aggregate is deployed in multiple threads and in multiple processes such that there are close to 1000 total pipeline threads, and the CAS rate going to the remote service is greater than about 100 per second.
> In this situation, which is common for a DUCC job, then the AMQ broker will start using an abnormally high amount of CPU while slowly delivering CASes to the remote service instances, resulting in poor throughput.
> Up until now the JMS service stub instantiates a new UimaAsynchronousEngine object for every thread. The problem does not occur if instead the JMS service stub instantiates a single UimaAsynchronousEngine object and uses it for all process threads pointing at the same remote service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)