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 A8D1E18B3D for ; Fri, 18 Sep 2015 06:32:19 +0000 (UTC) Received: (qmail 76823 invoked by uid 500); 18 Sep 2015 06:32:19 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 76773 invoked by uid 500); 18 Sep 2015 06:32:19 -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 76761 invoked by uid 99); 18 Sep 2015 06:32:19 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Sep 2015 06:32:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A53251A22C0 for ; Fri, 18 Sep 2015 06:32:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id LtrfDg10A0Xf for ; Fri, 18 Sep 2015 06:32:11 +0000 (UTC) Received: from smtp73.ord1c.emailsrvr.com (smtp73.ord1c.emailsrvr.com [108.166.43.73]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 9A00C4414C for ; Fri, 18 Sep 2015 06:32:11 +0000 (UTC) Received: from smtp26.relay.ord1c.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp26.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1508B380132; Fri, 18 Sep 2015 02:32:05 -0400 (EDT) Received: by smtp26.relay.ord1c.emailsrvr.com (Authenticated sender: reshu.agarwal-AT-orkash.com) with ESMTPSA id 6EC8A380100 for ; Fri, 18 Sep 2015 02:32:03 -0400 (EDT) X-Sender-Id: reshu.agarwal@orkash.com Received: from [192.168.0.117] ([UNAVAILABLE]. [14.141.49.198]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.4.2); Fri, 18 Sep 2015 06:32:05 GMT Message-ID: <55FBAFF4.9060807@orkash.com> Date: Fri, 18 Sep 2015 12:02:20 +0530 From: "reshu.agarwal" Organization: Orkash Services Pvt Ltd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: DUCC - Work Item Queue Time Management References: <55FA5834.9000802@orkash.com> <55FA7AB6.2080401@orkash.com> <55FB9205.7040401@orkash.com> In-Reply-To: <55FB9205.7040401@orkash.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit It looks like the class-path of job/service is not able to add successfully. On 09/18/2015 09:54 AM, reshu.agarwal wrote: > Jerry, > > I have tried DUCC 2.0.0 to run same job on it. I don't know why but > same job descriptor didn't work. It showed some exception at > initialization time which was not in case of 1.1.0. > > Is there any changes regarding job descriptor or service descriptor? > The both did not work in my case for DUCC 2.0.0 but for DUCC 1.0.0 and > DUCC 1.1.0. > > In Service descriptor it shows some spring Framework's class not found > exception. See below: > > *java.lang.NoClassDefFoundError: > org/springframework/context/ApplicationListener* > > Thanks in advance. > > Reshu. > > On 09/17/2015 08:15 PM, Jaroslaw Cwiklik wrote: >> Hi, can you try Ducc 2.0.0? It was recently released into Apache. One of >> the key changes was to remove queues as means of transport between JD >> (Job >> Driver) and JP (Job Process). Instead, each JP uses HTTP to request a >> Work >> Item (CAS) from a JD. >> >> DUCC 1.1.0 has a concept of a WI timeout which I think is 24 hours by >> default. A timer is started in a JD when each WI is dispatched to a >> JP. If >> the WI does not come back for whatever reason, the timer pops and a >> JD will >> attempt to retry that WI. >> >> To debug your problem with DUCC 1.1.0 I suggest attaching JMX console >> to a >> running JP to see where its threads are. Before doing this, check JP >> logs >> to see if there is an exception. >> >> Jerry >> >> >> >> On Thu, Sep 17, 2015 at 4:32 AM, reshu.agarwal >> >> wrote: >> >>> My DUCC version is 1.1.0. >>> >>> >>> On 09/17/2015 11:35 AM, reshu.agarwal wrote: >>> >>>> Hi, >>>> >>>> I am facing a problem in DUCC that some documents were shown in >>>> queue but >>>> did not get processed. In Job, work item list shows a particular work >>>> item's status "queued" and queueing time is "4115 seconds". >>>> >>>> I want to set queueing time of work item not more then 1 minute. >>>> What is >>>> the reason for the same? Is there any method to solve this? How can >>>> I set >>>> maximum queueing time for work item? >>>> >>>> Thanks in advance. >>>> >>>> Reshu. >>>> >>> > >