UIMA AS: Duplicate Request

[Jörn Kottmann <ko...@gmail.com>]

Hi,

there is this message in the service logs:
1/29/10 3:09:40 AM - 16: 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient: 
INF
O: Duplicate Request With Cas Reference Id: 2d0e21bb:12664a22384:7eac 
Received. Ignoring Duplicate.

What does it mean ? And how can it happen ?

Jörn

Re: UIMA AS: Duplicate Request

[Jörn Kottmann <ko...@gmail.com>]

Jaroslaw Cwiklik wrote:
> Jorn, are there any messages in the service log that say that the client is
> in the DoNotProcess List indicating a connection failure to the reply queue?
>   
No, there are two log messages (damn, its still in info log level mode, 
will change that)
at around the time the system failed:

1/29/10 3:09:40 AM - 16: 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient: 
INFO: Duplicate Request With Cas Reference Id: 2d0e21bb:12664a22384:7eac 
Received. Ignoring Duplicate.
1/29/10 3:36:45 AM - 23: 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel$ConnectionTimer.startTimer: 
INFO: Inactivity Timer Expired. Thread: Controller:SearchEngine:Reply 
TimerThread-:ID:dkcphlinh1master-49059-1264408732600-0:0:1:14749726442764009 
Controller: SearchEngine Timeout Value: 1,800,000 Endpoint Name: 
ID:dkcphlinh1master-49059-1264408732600-0:0:1(last message in the log file)

The Duplicate Request message has been a few times in the log file on 
other days.
> If this is not the case, can you confirm that there are messages in the
> service queue indicating that the service is hung somewhere.
>   
Yes there are messages in the service queue.

Maybe the hang issue from for a few days and the one today
have different reasons.

I kind of believe that the process method in my last AE after the CM 
blocked.
Add the end of the AE.process method it calls two web service methods, 
the first
to save analysis results, and the second to mark the article as processed.

In our database we could see that the first was called and the second 
method was never called,
but there was also no exception in the log files, which might indicated that
the process method just blocked at the end. There is no way to escape the
process method without throwing an exception or finishing the call, we
never received.

I hope I can provide you with more data when it happens again, so we can 
find the cause.
I will set timeouts on my web service calls, to make sure a blocked 
process method is not
the reason for the hang. Maybe there is also a timeout I can set for the 
process method.

 From the hang from a few days ago I have a core dump, but I am not sure 
how I can
find out where all the CASes are ... in the stack traces I can see that 
its trying to get
an empty cas in the CM.next() method but it seems like that its waiting 
for new CASes to
become available.

Jörn

Re: UIMA AS: Duplicate Request

[Jaroslaw Cwiklik <ui...@gmail.com>]

Jorn, are there any messages in the service log that say that the client is
in the DoNotProcess List indicating a connection failure to the reply queue?
If this is not the case, can you confirm that there are messages in the
service queue indicating that the service is hung somewhere.

JC

On Fri, Jan 29, 2010 at 11:26 AM, Jörn Kottmann <ko...@gmail.com> wrote:

> Jaroslaw Cwiklik wrote:
>
>> Jorn, the only thing that makes sense here is that the client is timing
>> out
>> while the service is still handling a CAS. Do you know if the client
>> resends
>> the same CAS after timeout?
>>
>>
> The client always calls getCAS() before it calls sendCAS(), and it assumes
> that it gets a fresh CAS from getCAS().
>
> I think I use the client API correctly, maybe that can happen if the client
> internally
> tries to send a CAS two times, maybe due a broker connection lost issue ...
> ?
>
> The UIMA AS Service also stopped processing messages afterwards, but I am
> not
> sure if that is related to the message.
>
> Jörn
>

Re: UIMA AS: Duplicate Request

[Jörn Kottmann <ko...@gmail.com>]

Jaroslaw Cwiklik wrote:
> Jorn, the only thing that makes sense here is that the client is timing out
> while the service is still handling a CAS. Do you know if the client resends
> the same CAS after timeout?
>   
The client always calls getCAS() before it calls sendCAS(), and it assumes
that it gets a fresh CAS from getCAS().

I think I use the client API correctly, maybe that can happen if the 
client internally
tries to send a CAS two times, maybe due a broker connection lost issue 
... ?

The UIMA AS Service also stopped processing messages afterwards, but I 
am not
sure if that is related to the message.

Jörn

Re: UIMA AS: Duplicate Request

[Jaroslaw Cwiklik <ui...@gmail.com>]

Jorn, the only thing that makes sense here is that the client is timing out
while the service is still handling a CAS. Do you know if the client resends
the same CAS after timeout?

JC

On Fri, Jan 29, 2010 at 4:26 AM, Jörn Kottmann <ko...@gmail.com> wrote:

> Hi,
>
> there is this message in the service logs:
> 1/29/10 3:09:40 AM - 16:
> org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient:
> INF
> O: Duplicate Request With Cas Reference Id: 2d0e21bb:12664a22384:7eac
> Received. Ignoring Duplicate.
>
> What does it mean ? And how can it happen ?
>
> Jörn
>