You dont have to use UimaAsynchronousEngine.getCAS() method to get CASes.
If you want to manage CASes yourself use CasCreationUtils. Here is a
javadoc for this class:
http://uima.apache.org/d/uimaj-2.4.0/apidocs/org/apache/uima/util/CasCreationUtils.html
JC
On Fri, Feb 3, 2012 at 3:10 AM, Spico
Hello!
Hmmm...My expectations regarding the UIMAASEngine capabilities were
different than the current implementations.In my opinion the client
shouldn't hang up due to the poor performance of the processing pipeline.
It should pump up all the created JCAS to the MQ queue, thus consumer(UIMA
AS s
On 2/2/2012 9:34 AM, Spico Florin wrote:
Hello!
Thank you for your answers. I'm using uima 2.3.1. Here is my testing code:
//Endpoint initialization
private int fsHeapSize = 200;
private int timeout = 600;
private int getmeta_timeout = 60;
private int cpc_timeout = 1;
Hello!
Thank you for your answers. I'm using uima 2.3.1. Here is my testing code:
//Endpoint initialization
private int fsHeapSize = 200;
private int timeout = 600;
private int getmeta_timeout = 60;
private int cpc_timeout = 1;
Map appCtx = new HashMap();
u
Sorry didnt finish my thought on question #1. If you see sendCAS()
blocking, attach jConsole to the application (you may need to enable JMX),
view the threads and check where your application thread is blocking.
JC
On Wed, Feb 1, 2012 at 9:52 AM, Jaroslaw Cwiklik wrote:
> Florin from you descri
Florin from you description I cant figure out the cause of the slowness
that you see. Are you saying that your application thread is stuck in
sendCAS() method as if it was waiting for a reply? This is certainly not
intent behind this API. It is an asynchronous call and should not wait for
a reply w
Are you following the examples in
http://uima.apache.org/downloads/releaseDocs/2.3.0-incubating/docs-uima-as/html/uima_async_scaleout/uima_async_scaleout.html#ugr.ref.async.api.usage
You may be limited by the size of the CAS pool (see the example code for how to
set this).
-Marshall
On 2/1/20
Hello!
I have application client that is receiving messages from a Queue via JMS.
The message is then packed in a JCas and sent to the UIMA AS pipeline via
UimaAsynchronousEngine.
If the UIMA AS pipeline processing is slow then it impacts the client in
the way that the received messages from the
Qu
