uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jaroslaw Cwiklik <cwik...@us.ibm.com>
Subject Re: UimaASProcessCasTimeout exception hangs application
Date Tue, 07 Oct 2008 13:34:57 GMT

Charles, this appears to be a bug in the UIMA AS client code. The only work
around that comes to mind right now
is to run without -i. Without -i the  runRemoteAE should  terminate on

We will investigate this problem and post a patch on apache.


Jerry Cwiklik
 UIMA Extensions
 IBM T.J.  Watson Research Center
 Hawtorne, NY, 10532
 Tel: 914-784-7665,  T/L: 863-7665
 Email: cwiklik@us.ibm.com

             Charles Proefrock                                             
             .com>                                                      To 
                                       UIMA User                           
             10/06/2008 05:59          <uima-user@incubator.apache.org>    
             PM                                                         cc 
             Please respond to         UimaASProcessCasTimeout exception   
             uima-user@incubat         hangs application                   

When experimenting with the UIMA-AS examples and how the error handling
mechanisms work in terms of timeouts due to AS Aggregates taking too long
or going offline, we came across a situation in which the RunRemoteAsyncAE
hangs and never returns after receiving and processing a
UimaASProcessCasTimeout exception.  Ultimately, we simply want the system
to recover and try the next CAS or return gracefully without having to call
a hard System.exit(1).

Our tests are based on the Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml
example.  All we did was the following:
(1)   added “Thread.sleep(5000);” to RoomNumberAnnotator.java process to
simulate  a longer process.
(2)   Executed: startBroker.bat
(3)   Executed: deployAsyncService <DIR>\Deploy_RoomNumberAnnotator.xml
(4)   Executed: runRemoteAsyncAE tcp://localhost:61616
MeetingDetectorTaeQueue –c <DIR>\FileSystemCollectionReader.xml -t 4 -i

In summary: when setting and triggering the time outs on the RoomNumber
remoteAnalysisEngine, the exception is thrown and caught, each additional
CAS is tried, and the system exists gracefully.  If the
UimaAsynchronousEngine within the runRemoteAsyncAE times out, then the
system hangs and never returns.

Is there a trick that we’re missing? Is this expected?

- Charles

See how Windows Mobile brings your life together—at home, work, or on the
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message