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 2006/11/15 17:34:46 UTC

[jira] Created: (UIMA-33) Do not use same timeout on GetMetadata as is used for Process

Do not use same timeout on GetMetadata as is used for Process
-------------------------------------------------------------

                 Key: UIMA-33
                 URL: http://issues.apache.org/jira/browse/UIMA-33
             Project: UIMA
          Issue Type: Improvement
          Components: Transport Adapters - SOAP, Vinci
            Reporter: Adam Lally
            Priority: Minor


The Vinci client descriptor currently has one timeout setting, which is used for all operations, including the GetMetaData call and the Process call.  For services that do very expensive processing, this timeout must be set to a large value so that the Process call can complete.  However there's no reason that the timeout should be so large for the GetMetaData call.  

This is an issue because if the service is hung, it would be nice if GetMetaData (the first call that the client makes) would return an error after a relatively short amount of time, rather than waiting for the full process timeout to elapse (which could be several minutes, or more).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] Assigned: (UIMA-33) Do not use same timeout on GetMetadata as is used for Process

Posted by Adam Lally <al...@alum.rpi.edu>.
On 12/11/06, Adam Lally (JIRA) <ui...@incubator.apache.org> wrote:
>      [ http://issues.apache.org/jira/browse/UIMA-33?page=all ]
>
> Adam Lally reassigned UIMA-33:
> ------------------------------
>
>     Assignee: Adam Lally
>
> > Do not use same timeout on GetMetadata as is used for Process
><snip/>

I changed the Vinci client stub so that the timeout value specified in
the client descriptor is used only for process and
collectionProcessComplete, not for getMetadata.

getMetadata uses the default Vinci timeout of 2 minutes.  Is this
sufficient, or do we need to make this configurable?  I can't see much
of a need to tweak this value.

-Adam

[jira] Closed: (UIMA-33) Do not use same timeout on GetMetadata as is used for Process

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/UIMA-33?page=all ]

Adam Lally closed UIMA-33.
--------------------------

    Fix Version/s: 2.1
       Resolution: Fixed

> Do not use same timeout on GetMetadata as is used for Process
> -------------------------------------------------------------
>
>                 Key: UIMA-33
>                 URL: http://issues.apache.org/jira/browse/UIMA-33
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Transport Adapters - SOAP, Vinci
>            Reporter: Adam Lally
>         Assigned To: Adam Lally
>            Priority: Minor
>             Fix For: 2.1
>
>
> The Vinci client descriptor currently has one timeout setting, which is used for all operations, including the GetMetaData call and the Process call.  For services that do very expensive processing, this timeout must be set to a large value so that the Process call can complete.  However there's no reason that the timeout should be so large for the GetMetaData call.  
> This is an issue because if the service is hung, it would be nice if GetMetaData (the first call that the client makes) would return an error after a relatively short amount of time, rather than waiting for the full process timeout to elapse (which could be several minutes, or more).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Assigned: (UIMA-33) Do not use same timeout on GetMetadata as is used for Process

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/UIMA-33?page=all ]

Adam Lally reassigned UIMA-33:
------------------------------

    Assignee: Adam Lally

> Do not use same timeout on GetMetadata as is used for Process
> -------------------------------------------------------------
>
>                 Key: UIMA-33
>                 URL: http://issues.apache.org/jira/browse/UIMA-33
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Transport Adapters - SOAP, Vinci
>            Reporter: Adam Lally
>         Assigned To: Adam Lally
>            Priority: Minor
>
> The Vinci client descriptor currently has one timeout setting, which is used for all operations, including the GetMetaData call and the Process call.  For services that do very expensive processing, this timeout must be set to a large value so that the Process call can complete.  However there's no reason that the timeout should be so large for the GetMetaData call.  
> This is an issue because if the service is hung, it would be nice if GetMetaData (the first call that the client makes) would return an error after a relatively short amount of time, rather than waiting for the full process timeout to elapse (which could be several minutes, or more).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira