You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2011/02/22 20:16:38 UTC

[jira] Closed: (UIMA-2068) Modify UIMA AS broker configuration file to include optimizedDispatch="true"

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

Jerry Cwiklik closed UIMA-2068.
-------------------------------

    Resolution: Fixed

Added optimizedDispatch="true" to broker config file

> Modify UIMA AS broker configuration file to include optimizedDispatch="true"
> ----------------------------------------------------------------------------
>
>                 Key: UIMA-2068
>                 URL: https://issues.apache.org/jira/browse/UIMA-2068
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3.1AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> Running a broker with optimizedDispatch="true" yields much better performance. Without this setting the broker is really slow under heavy load. By default, AMQ uses two threads per each jms session: transport thread and a session thread. With optimizedDispatch=true only one thread is used: the transport thread.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira