[
https://issues.apache.org/jira/browse/UIMA-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik resolved UIMA-1725.
---------------------------------
Resolution: Won't Fix
No longer needed
> UIMA AS should provide a way to change the Process Timeout dynamically
> -----------------------------------------------------------------------
>
> Key: UIMA-1725
> URL: https://issues.apache.org/jira/browse/UIMA-1725
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> There is a need to provide a finer level of control over the Process Timeout
> setting. Currently, UIMA AS client's Process Timeout defaults to 60 secs and
> can be overriden by an application during initialization of the client. Once
> set, it remains the same for the duration of the client. There is no way to
> change it in the middle of the run. Some applications may need to adjust the
> timeout on per CAS basis. The same functionality (dynamically controlled
> timeout) may also be useful for UIMA AS services. The exact mechanism for
> implementing this new feature is up for debate. For UIMA AS client, perhaps a
> new client API can be added to change the timeout value. The application
> would change the timeout, call send ( synchronous or asynchronous), and
> change the timeout value back to what it was when the reply is received.
> Another approach would be to add the timeout value to the CAS and have the
> UIMA AS client check for it before forwarding the CAS to a service. Yet
> another approach would be JMX, although this seems cumbersome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
