You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Adam Lally (JIRA)" <ui...@incubator.apache.org> on 2008/02/25 17:40:51 UTC

[jira] Created: (UIMA-821) Vinci Services have getMetaData timeout problems when there are a large number of clients

Vinci Services have getMetaData timeout problems when there are a large number of clients
-----------------------------------------------------------------------------------------

                 Key: UIMA-821
                 URL: https://issues.apache.org/jira/browse/UIMA-821
             Project: UIMA
          Issue Type: Bug
          Components: Transport Adapters - SOAP, Vinci
    Affects Versions: 2.2.1
            Reporter: Adam Lally
            Assignee: Adam Lally
             Fix For: 2.2.2


When I have a large number of clients I am experiencing timeouts in the getMetadata call.  There's currently no way to configure this timeout - in issue UIMA-33, we made the client descriptor's <timeout> element apply only to the process call, so getMetadata defaults to a 1 minute timeout.  With a small number of clients this is OK, but the Vinci service has a default thread pool of size 20 (also not configurable through the UIMA descriptor), so if you have more clients than this then this pool may get filled up with process requests forcing a getMetadata call to wait much longer.  Probably both of these settings should be configurable.

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


[jira] Closed: (UIMA-821) Vinci Services have getMetaData timeout problems when there are a large number of clients

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally closed UIMA-821.
---------------------------

    Resolution: Fixed

Added ability to configure getMetaData timeout in the service client descriptor and the thread pool min/max sizes in the deployment descriptor.  Documentation included.

> Vinci Services have getMetaData timeout problems when there are a large number of clients
> -----------------------------------------------------------------------------------------
>
>                 Key: UIMA-821
>                 URL: https://issues.apache.org/jira/browse/UIMA-821
>             Project: UIMA
>          Issue Type: Bug
>          Components: Transport Adapters - SOAP, Vinci
>    Affects Versions: 2.2.1
>            Reporter: Adam Lally
>            Assignee: Adam Lally
>             Fix For: 2.2.2
>
>
> When I have a large number of clients I am experiencing timeouts in the getMetadata call.  There's currently no way to configure this timeout - in issue UIMA-33, we made the client descriptor's <timeout> element apply only to the process call, so getMetadata defaults to a 1 minute timeout.  With a small number of clients this is OK, but the Vinci service has a default thread pool of size 20 (also not configurable through the UIMA descriptor), so if you have more clients than this then this pool may get filled up with process requests forcing a getMetadata call to wait much longer.  Probably both of these settings should be configurable.

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