I also see that the -t process timeout value has to be > 10 for this to succeed ... I'd have assumed anything > 5 secs would be safe, but the default value of -p 2 means that the client's timeout must be 2x the service process time when 2 CASes are in play, since the 2nd is queued immediately behind the first. Perhaps the default should be -p 1 for simplicity.
P.S. I assume you meant RoomNumberAnnotatorQueue as the 2nd arg in step 4. On Tue, Oct 7, 2008 at 9:34 AM, Jaroslaw Cwiklik <[EMAIL PROTECTED]> wrote: > 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 > exception. > > We will investigate this problem and post a patch on apache. > > Thanks > > Jerry > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Jerry Cwiklik > UIMA Extensions > IBM T.J. Watson Research Center > Hawtorne, NY, 10532 > Tel: 914-784-7665, T/L: 863-7665 > Email: [EMAIL PROTECTED] > > [image: Inactive hide details for Charles Proefrock <[EMAIL > PROTECTED]>]Charles > Proefrock <[EMAIL PROTECTED]> > > > > *Charles Proefrock <[EMAIL PROTECTED]>* > > 10/06/2008 05:59 PM > Please respond to > [email protected] > > > To > > UIMA User <[email protected]> > cc > > > Subject > > UimaASProcessCasTimeout exception 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 > go. > http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/ >
