Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of uimaee@gmail.com designates
 209.85.160.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=ux3fpHz8xpE6S85vFz5jJftVot3yEwbY4qgY5pwmg5rQMGNhGATV4fgV1x6Jtq94HH
         A9VwJuM3LWDCe+gU+C7NPPKUo6cBtWgXbIFtnCObxukq54IhybTIeFDjmxGbeD1+IBSQ
         TxGbCMd+qvyhOeIZlcCKUSywf77+hf9T7612c=
MIME-Version: 1.0
In-Reply-To: <4BB1C759.7030306@yahoo.fr>
References: <4BB1C759.7030306@yahoo.fr>
Date: Wed, 31 Mar 2010 09:52:07 -0400
Message-ID: <n2ufe44bdb91003310652qd5920d00raf25f57e178f4b95@mail.gmail.com>
Subject: Re: UIMA-AS client is blocking
From: Jaroslaw Cwiklik <uimaee@gmail.com>
To: uima-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e64ca50454b1b10483190ddc

--0016e64ca50454b1b10483190ddc
Content-Type: text/plain; charset=ISO-8859-1

You are not calling cas.release() when you are done with the CAS.
Per UIMA AS documentation ("4.2 The UimaAsynchronousEngine Interface - CAS
getCAS()"

"...CAS getCAS(): Requests a new CAS instance from the CAS pool. This method
blocks until a free instance of CAS is available in the CAS pool.
Applications that
use getCAS() need to call CAS.reset() before reusing the CAS, or
CAS.release()
to return it to the Cas pool."

The release() places a CAS back into the pool so the subsequent call to
getCAS()
succeeds. An alternate strategy is to have a single CAS instance in the CAS
pool
call getCAS() to get that instance and enter a while loop. When done
processing
reply, call cas.reset() and do *not* call getCAS() again.

JC

On Tue, Mar 30, 2010 at 5:41 AM, pierre yahoo <ppujalon@yahoo.fr> wrote:

> I'm trying to use UIMA-AS to scale a part of the process of our
> application.
> I have successfully deployed our process as asynchronous services but I
> have tremendous issues with the client.
>
> I'm basically looping synchronously(one at a time) on the following code.
>     CAS cas = uimaEEEngine.getCAS();
>     JCas jcas;
>     try {
>        jcas = cas.getJCas();
>     } catch (CASException e) {
>         throw new ResourceProcessException(e);
>     }
>     fillCas(jcas);
>     uimaEEEngine.sendCAS(cas);
>
> When I run the application, the client works fine for a while and suddenly
> gets stuck waiting on cas.getJCas()..
> I have checked that the asynchronous service have processed all the
> previous  CAS.  The service is still up and running as I can send requests
> from an another client.
> When I tracked down who locks the process, I can see that the semaphore on
> CasQueueEntry is not released.
> When I looked further, I noticed that the all process is basically lock
> when the CasManager_Impl is calling CasPool.getCas(0) . The CasPool is then
> waiting with no timeout for someone to notify it.
>
> I try to change the size of the client CasPool but it didn't really fix the
> issue. Just pushing further the lock...
>
> Does anyone have ever experienced this? Am I doing something wrong ?
>
> Pierre
>

--0016e64ca50454b1b10483190ddc--