uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Parente (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-2392) UIMA-AS CAS multiplier hangs fetching empty CAS after client timeouts
Date Wed, 02 May 2012 16:54:54 GMT

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

Peter Parente updated UIMA-2392:

    Attachment: logs.zip

Logs. Clean = run with timeout set to 0 (infinite). Hang = 2 client runs with timeout set
to 8000ms as in the test case.
> UIMA-AS CAS multiplier hangs fetching empty CAS after client timeouts
> ---------------------------------------------------------------------
>                 Key: UIMA-2392
>                 URL: https://issues.apache.org/jira/browse/UIMA-2392
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3.1AS
>         Environment: RedHat Enterprise Linux 6.0, Mac OSX Lion 10.7.3
>            Reporter: Peter Parente
>              Labels: ibm
>         Attachments: logs.zip, uima-hang.zip
> I'm attaching a test case that reproduces the hang. See the README inside the zip about
how to execute it.
> The annotator (ForwardJCas) consists of a simple CAS multiplier with delays in it scaled
out in its own thread within 2 levels of aggregates. It receives a CAS, sleeps for 3 seconds,
gets a new empty CAS, copies information into it, sleeps again, and then returns the CAS.
The unit test (UimaAsTest) initializes 40 UIMA-AS clients with a timeout of 8 seconds, send
1 CAS from each to the service, and then waits. After 1-2 runs, the CAS multiplier winds up
hanging on the getEmptyCas() call in the scaled out annotator. 
> What appears to be happening is that free CAS messages are not being sent from the client
to the service in all cases when the timeouts occur. A similar defect (https://issues.apache.org/jira/browse/UIMA-1786)
was fixed in 2.3.1 with slightly different symptoms.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message