I've checked the code and indeed this is a bug in uima-as client when
running with a CR. As soon as the CR
returns false from hasNext() the uima-as client process() method calls
collectionProcessComplete().
The fix for this is to wait until all outstanding CASes are processed
before calling
Thanks Jerry. BTW will we be seeing a UIMA-AS 2.4.0 sometime soon?
Thanks,
Thomas Ginter
801-448-7676
thomas.gin...@utah.edu
On Jun 20, 2012, at 1:03 PM, Jaroslaw Cwiklik wrote:
I've checked the code and indeed this is a bug in uima-as client when
running with a CR. As soon as the CR
Yes, I am working on the next release. Cant commit to a specific date yet.
Jerry
On Wed, Jun 20, 2012 at 3:06 PM, Thomas Ginter thomas.gin...@utah.eduwrote:
Thanks Jerry. BTW will we be seeing a UIMA-AS 2.4.0 sometime soon?
Thanks,
Thomas Ginter
801-448-7676
thomas.gin...@utah.edu
My UIMA-AS 2.3.1 service is returning the CollectionProcessComplete event while
there are still CAS objects outstanding. The client log shows:
INFO: Client in CollecitonProcessComplete - OutstandingCasCount=2
TotalCasRequestsSentBetweenCpCs=
I always seem to end up losing 2 CAS objects
