uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Closed] (UIMA-5784) UIMA-AS: MessageTimeOutException not available to client on init failure
Date Fri, 04 Jan 2019 14:38:00 GMT

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

Jerry Cwiklik closed UIMA-5784.
-------------------------------
    Resolution: Fixed

Include cause of error when replying to client with an error

> UIMA-AS: MessageTimeOutException not available to client on init failure
> ------------------------------------------------------------------------
>
>                 Key: UIMA-5784
>                 URL: https://issues.apache.org/jira/browse/UIMA-5784
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.10.4AS
>
>
> When an aggregate times out waiting for delegate GetMeta response, it does not include
MessageTimeoutException as cause in an exception going back to the deployer. Instead is just
provides ResourceInitializationException with no real cause. Some clients may need to know
this in order to decide whether or not to retry uima-as initialization. 
> In a specific case, a client deploys an aggregate with one of its delegates not yet available. 
> Also fix service log message as it says: 
> org.apache.uima.aae.error.MessageTimeoutException: Delegate Service:NoOp Has Timed Out
While Processing CAS:null
> In this case, the timeout was related to GetMeta. The message should clearly state what
operation has timed out. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message