[ https://issues.apache.org/jira/browse/UIMA-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1742: --------------------------------- Fix Version/s: 2.3.1AS > UIMA AS Aggregate not exposing number of consumer threads on its delegate's > reply queues > ---------------------------------------------------------------------------------------- > > Key: UIMA-1742 > URL: https://issues.apache.org/jira/browse/UIMA-1742 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Affects Versions: 2.3AS > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > Priority: Minor > Fix For: 2.3.1AS > > > UIMA AS Spring listener uses a single thread per delegate to handle replies. > If a deployment descriptor is configured to process replies using multiple > threads, the UIMA AS creates a concurrent listener with a thread pool to > which the single-threaded Spring listener delegates all reply messages. This > logic was added to assure that the parent CAS is always processed ahead of > its children. The problem is that a JMX console shows a single JMS Consumer > on a reply queue. This is correct, but the number of threads in the > concurrent listener should be shown in the UIMA AS MBeans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.