Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5ADB210BC9 for ; Thu, 3 Apr 2014 05:24:00 +0000 (UTC) Received: (qmail 95245 invoked by uid 500); 3 Apr 2014 05:23:59 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 94990 invoked by uid 500); 3 Apr 2014 05:23:58 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 94967 invoked by uid 99); 3 Apr 2014 05:23:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 05:23:56 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [108.166.43.113] (HELO smtp113.ord1c.emailsrvr.com) (108.166.43.113) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 05:23:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D1C161B8A0A; Thu, 3 Apr 2014 01:23:28 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: reshu.agarwal-AT-orkash.com) with ESMTPSA id 41F471B883F for ; Thu, 3 Apr 2014 01:23:28 -0400 (EDT) Message-ID: <533CF089.9090000@orkash.com> Date: Thu, 03 Apr 2014 10:54:25 +0530 From: "reshu.agarwal" Organization: Orkash Services Pvt Ltd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: Cas Timeout Exception in DUCC References: <53354685.5030000@orkash.com> <53354C5A.6000404@orkash.com> <53390E65.2070606@orkash.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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 wrote: > >> On 03/28/2014 05:36 PM, Eddie Epstein wrote: >> >>> There is a job specification parameter: >>> --process_per_item_time_max >>> 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 >>> 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.AbstractJdProcessExceptionHandler: >>>> 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.AbstractJdProcessExceptionHandler: >>>> 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 >> 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