uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie Epstein <eaepst...@gmail.com>
Subject Re: Cas Timeout Exception in DUCC
Date Fri, 04 Apr 2014 12:11:18 GMT
Reshu,

Can you zip up the logfile directory for one of these failing jobs and make
it available for download?

Eddie


On Thu, Apr 3, 2014 at 1:24 AM, reshu.agarwal <reshu.agarwal@orkash.com>wrote:

> On 03/31/2014 04:37 PM, Eddie Epstein wrote:
>
>> Reshu,
>>
>> Please look in the logfile of the job process. Maybe 10 minutes is still
>> not enough?
>>
>> Eddie
>>
>>
>> On Mon, Mar 31, 2014 at 2:42 AM, reshu.agarwal <reshu.agarwal@orkash.com>
>> wrote:
>>
>>  On 03/28/2014 05:36 PM, Eddie Epstein wrote:
>>>
>>>  There is a job specification parameter:
>>>> --process_per_item_time_max <integer>
>>>>                 Maximum elapsed time (in minutes) for processing one
>>>> CAS.
>>>>
>>>> Try setting that to something big enough.
>>>>
>>>> Eddie
>>>>
>>>>
>>>> On Fri, Mar 28, 2014 at 6:18 AM, reshu.agarwal <
>>>> reshu.agarwal@orkash.com>
>>>> wrote:
>>>>
>>>>   On 03/28/2014 03:23 PM, reshu.agarwal wrote:
>>>>
>>>>>   Cas Timed-out on hos
>>>>>
>>>>>>   Hi,
>>>>>>
>>>>> JD.log contains this:
>>>>>
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.aae.delegate.Delegate$1
>>>>> Delegate.TimerTask.run
>>>>> WARNING: Timeout While Waiting For Reply From
>>>>> Delegate:ducc.jd.queue.1887
>>>>> Process CAS Request Timed Out. Configured Reply Window Of 180,000. Cas
>>>>> Reference Id:-139073d5:145080818b3:-7f7c
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.adapter.jms.
>>>>> client.ActiveMQMessageSender
>>>>> run
>>>>> INFO: UIMA AS Client Message Dispatcher Sending GetMeta Ping To the
>>>>> Service
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.adapter.jms.client.
>>>>> BaseUIMAAsynchronousEngineCommon_impl sendCAS
>>>>> INFO: Uima AS Client Sent PING Message To Service: ducc.jd.queue.1887
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.adapter.jms.
>>>>> client.ClientServiceDelegate
>>>>> handleError
>>>>> WARNING: Process Timeout - Uima AS Client Didn't Receive Process Reply
>>>>> Within Configured Window Of:180,000 millis
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.adapter.jms.client.
>>>>> BaseUIMAAsynchronousEngineCommon_impl notifyOnTimout
>>>>> WARNING: Request To Process Cas Has Timed-out. Service
>>>>> Queue:ducc.jd.queue.1887. Broker: tcp://S1:61616?wireFormat.
>>>>> maxInactivityDuration=0&jms.useCompression=true&closeAsync=false
Cas
>>>>> Timed-out on host: 192.168.......
>>>>> Mar 28, 2014 3:07:10 PM org.apache.uima.adapter.jms.client.
>>>>> BaseUIMAAsynchronousEngineCommon_impl sendAndReceiveCAS
>>>>> INFO: UIMA AS Handling Exception in sendAndReceive(). CAS
>>>>> hashcode:1432981672. ThreadMonitor Released Semaphore For Thread ID:42
>>>>> org.apache.uima.ducc.common.jd.plugin.AbstractJdProcessExceptionHand
>>>>> ler:
>>>>> org.apache.uima.aae.error.UimaASProcessCasTimeout: UIMA AS Client
>>>>> Timed
>>>>> Out Waiting for Reply From Service:ducc.jd.queue.1887
>>>>> Broker:tcp://S1:61616?
>>>>> wireFormat.maxInactivityDuration=0&jms.useCompression=true&
>>>>> closeAsync=false
>>>>> org.apache.uima.ducc.common.jd.plugin.AbstractJdProcessExceptionHand
>>>>> ler:
>>>>> directive=ProcessContinue_CasNoRetry, [192.168.....:5729]=1, [total]=1
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Reshu Agarwal
>>>>>
>>>>>
>>>>>   Dear Eddie,
>>>>>
>>>> If I set it to greater then 3 minutes i.e 10 minutes, it still showed
>>> timed out error and did not terminate the job by itself. So, it did not
>>> work for me.
>>>
>>>
>>> --process_per_item_time_max <integer>
>>>                Maximum elapsed time (in minutes) for processing one CAS.
>>>
>>>
>>> --
>>> Thanks,
>>> Reshu Agarwal
>>>
>>>
>>>  HI Eddie,
>
> If I increase the process_per_item_time_max, the job is keep waiting for
> that time and still terminates some jobs with the same error and it is not
> like, that particular job is taking this much time as if I run same job
> again that job runs without any error.
>
> --
> Thanks,
> Reshu Agarwal
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message