Eddie Epstein created UIMA-3519:
-----------------------------------
Summary: 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
Fix For: 2.4.2AS
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.1.5#6160)
