Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE69110CBC for ; Mon, 10 Mar 2014 21:47:50 +0000 (UTC) Received: (qmail 98268 invoked by uid 500); 10 Mar 2014 21:47:49 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 98149 invoked by uid 500); 10 Mar 2014 21:47:49 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 98142 invoked by uid 99); 10 Mar 2014 21:47:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 21:47:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of samindaw@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-la0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 21:47:43 +0000 Received: by mail-la0-f41.google.com with SMTP id gl10so5202149lab.28 for ; Mon, 10 Mar 2014 14:47:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=AgZKnF51ge7cj3F5AHEZGKR6KaZe0Ya0ne6w16lqwEM=; b=UNZZaT/YIypU9Kn3mSb/Mof21e8l+/+t9EY4fwioukgif+/zGOVbwAq4386VJiIVg8 KEOX/I/u6TmcxNe/wUrHw3HM6QajY3wEdMxTejL/cTLFgWMi2OGIQwGRepPSPo5fiyWO iDK9QrSmPVia0U5a+JxGyVa7lAO71JvWewze2Xk2vfWjYiQPfdyr0QYktKvc3E5eaAuB ugS0ZqqxeWv3t33t7RynNZbdrOTfZlXY9e5USYhSpe0Upzbcryb+hTqWWFDVwQdULB4s YK+p/NyzK1AjZCQJwoynVItlUReD7vaVU71wOBpm+w9w5ya7jgPH22sBBL7zDFnuTYUI a1bQ== X-Received: by 10.152.9.1 with SMTP id v1mr24928394laa.31.1394488042338; Mon, 10 Mar 2014 14:47:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.58.130 with HTTP; Mon, 10 Mar 2014 14:47:02 -0700 (PDT) In-Reply-To: References: From: Saminda Wijeratne Date: Mon, 10 Mar 2014 17:47:02 -0400 Message-ID: Subject: Re: Updates to Airavata Server Startup To: dev Content-Type: multipart/alternative; boundary=089e0158b7c2683cad04f4478c65 X-Virus-Checked: Checked by ClamAV on apache.org --089e0158b7c2683cad04f4478c65 Content-Type: text/plain; charset=ISO-8859-1 I managed to reproduce this when an experiment is launched by the server. The stop command will not return until it detects that the servers have being stopped. Seems some thread(s) could hogging the whole process causing the server to get any process time to execute stop. I'm looking at this issue at the moment. On Mon, Mar 10, 2014 at 4:24 PM, Raminder Singh wrote: > Hi Saminda, > > I am not able to stop the server using ./airavata-server.sh stop. I am > getting following log message and it stays like that. > > [INFO] Requesting airavata server(s) to stop... > > Another suggestion is to have a rolling file logs for the server. That way > if user restarts the service, old logs are not lost. > > Thanks > Raminder > > > On Mar 10, 2014, at 11:20 AM, Saminda Wijeratne > wrote: > > We should be able to. Should it be a server implementation level > configuration? If so can be put it in the server properties? > > > On Mon, Mar 10, 2014 at 10:20 AM, Lahiru Gunathilake wrote: > >> Hi Saminda, >> >> Can we support TThreadPoolServer and make it configurable ? >> >> Regards >> Lahiru >> >> >> On Mon, Mar 10, 2014 at 8:54 AM, Saminda Wijeratne wrote: >> >>> A few updates to the standalone server startup [1], >>> >>> >>> 1. Start the server as a daemon when needed >>> - eg: $./airavata-server.sh start >>> 2. Stop the server (daemon or otherwise) >>> - eg: $./airavata-server.sh stop >>> 3. What servers to start are mentioned in the server properties file >>> ("servers=..."). The servers will start in the given order >>> - eg: servers=apiserver,orchestrator >>> 4. Command line parameters of the form "--=" >>> updates or overrides existing server configs. >>> - eg: $./airavata-server.sh --servers=orchestrator >>> --myproxy.user=ogce --myproxy.pass=mpass >>> >>> >>> TODO: >>> >>> 1. Update the integration-test pom to start airavata server [2] >>> 2. The windows batch script needs to be updated. >>> >>> >>> >>> 1. https://issues.apache.org/jira/browse/AIRAVATA-1045 >>> 2. https://issues.apache.org/jira/browse/AIRAVATA-1054 >>> >> >> >> >> -- >> System Analyst Programmer >> PTI Lab >> Indiana University >> > > > --089e0158b7c2683cad04f4478c65 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I managed to reproduce this when an experiment is launched= by the server. The stop command will not return until it detects that the = servers have being stopped. Seems some thread(s) could hogging the whole pr= ocess causing the server to get any process time to execute stop. I'm l= ooking at this issue at the moment.


On Mon,= Mar 10, 2014 at 4:24 PM, Raminder Singh <rsandhu1@gmail.com> wrote:
Hi Samin= da,

I am not able to stop the server using ./airavata-se= rver.sh stop. I am getting following log message and it stays like that.&nb= sp;
 
[INFO] Requesting airavata server(s) to stop…<= /div>

Another suggestion is to have a rolling file logs = for the server. That way if user restarts the service, old logs are not los= t. 

Thanks
Raminder

=

On Mar 10, 2014, at 11:20 AM, Saminda Wijeratne <samindaw@gmail.com&= gt; wrote:

We should be able to. Should= it be a server implementation level configuration? If so can be put it in = the server properties?


On Mon, Mar 10, 2014 at 10:20 AM, Lahiru Gunathilake <= glahiru@gmail.com> wrote:
Hi Saminda,

<= div>Can we support TThreadPoolServer and mak= e it configurable ?

Regards
Lahiru


On Mon, Mar 10, 2014 at 8:54 AM, Saminda Wijeratne = <samindaw@gmail.= com> wrote:
A few updates to = the standalone server startup [1],

  1. Start the server as= a daemon when needed
    • eg: $./airavata-server.sh start
  2. Stop the server (daemo= n or otherwise)
    • eg: $./airavata-server.sh stop
  3. What servers to start a= re mentioned in the server properties file ("servers=3D<server1>= <server2>..."). The servers will start in the given order
    • eg: servers=3Dapiserver,orchestrator
  4. Command line para= meters of the form "--<arg-key>=3D<arg-value>" update= s or overrides existing server configs.
    • eg: $./airavata-server.= sh --servers=3Dorchestrator --myproxy.user=3Dogce --myproxy.pass=3Dmpass

TODO:
  1. Update= the integration-test pom to start airavata server [2]
  2. The windows = batch script needs to be updated.



<= font color=3D"#888888">--
System Analyst Programmer
PTI Lab
Indiana University



--089e0158b7c2683cad04f4478c65--