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 1A33811767 for ; Thu, 31 Jul 2014 12:45:21 +0000 (UTC) Received: (qmail 44063 invoked by uid 500); 31 Jul 2014 12:45:20 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 44020 invoked by uid 500); 31 Jul 2014 12:45:20 -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 44009 invoked by uid 99); 31 Jul 2014 12:45:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 12:45:20 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [108.166.43.105] (HELO smtp105.ord1c.emailsrvr.com) (108.166.43.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 12:45:15 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id EC652807C3; Thu, 31 Jul 2014 08:44:53 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: reshu.agarwal-AT-orkash.com) with ESMTPSA id 4646880764 for ; Thu, 31 Jul 2014 08:44:53 -0400 (EDT) X-Sender-Id: reshu.agarwal@orkash.com Received: from [192.168.0.117] ([UNAVAILABLE]. [14.141.49.198]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA) by 0.0.0.0:465 (trex/5.2.10); Thu, 31 Jul 2014 12:44:53 GMT Message-ID: <53DA3A76.8080304@orkash.com> Date: Thu, 31 Jul 2014 18:15:42 +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: problem in calling DUCC Service with ducc_submit References: <533A4E51.2010604@orkash.com> <53D9E52D.8090507@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 Dear Burn, Thanks for the information. But problem is as Eddie Said before, we can not use the DUCC Service using ducc_submit, we can just check availability of service by using service_dependency in job. There is only a way that I have to create a Analysis Engine which is using ducc service using UIMA AS client. If there is another way to use DUCC Service in Job so I can use DUCC Service as my AE or DD, then please tell me. On 07/31/2014 06:05 PM, Burn Lewis wrote: > You can register a DUCC service with --autostart set to true and the > service will start when it is registered and stay running. If your job has > a dependency on that service DUCC will verify that it is running before > starting your job. > If instead you register the service without autostart then DUCC will start > the service (if it is not already running) before starting your job. When > the last job that references that service ends DUCC will stop the service > after an idle delay defined by the service's --linger value. If you make > linger very large the service can be made to stay running, even if it is > idle, for many hours between jobs. > > ~Burn > > > On Thu, Jul 31, 2014 at 2:41 AM, reshu.agarwal > wrote: > >> Hi, >> >> Today, I got understand the reason of why DUCC Job is not using DUCC >> Service. But All I want that my initialization Part of a Process_DD should >> occur once. I don't need to wait every time for initialization. So, I want >> to use DUCC Service in my DUCC JOB. >> >> Is there any way to configure in DUCC that Process_DD initialized once and >> Job will start again and again? >> >> On 04/01/2014 05:21 PM, Eddie Epstein wrote: >> >>> Declaring a service dependency does not affect application code paths. The >>> job still needs to connect to the service in the normal way. >>> >>> DUCC uses services dependency for several reasons: to automatically start >>> services when needed by a job; to not give resources to a job or service >>> for which a dependent service is not running; and to post a warning on >>> running jobs when a dependent service goes "bad". >>> >>> Eddie >>> >>> >>> On Tue, Apr 1, 2014 at 1:27 AM, reshu.agarwal >>> wrote: >>> >>> Hi, >>>> I am again in a problem. I have successfully deployed DUCC UIMA AS >>>> Service >>>> using ducc_service. The service status is available with good health. If >>>> I >>>> try to use my this service using parameter service_dependency to my Job >>>> in >>>> ducc_submit then it is not showing any error but executes only the DB >>>> Collection Reader not this service. >>>> >>>> -- >>>> Thanks, >>>> Reshu Agarwal >>>> >>>> >>>> >> -- >> Thanks, >> Reshu Agarwal >> >> -- Thanks, Reshu Agarwal