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 355D410857 for ; Fri, 15 Nov 2013 03:22:18 +0000 (UTC) Received: (qmail 21936 invoked by uid 500); 15 Nov 2013 03:22:13 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 21822 invoked by uid 500); 15 Nov 2013 03:22:08 -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 21810 invoked by uid 99); 15 Nov 2013 03:22:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Nov 2013 03:22:06 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nipuni880917@gmail.com designates 209.85.212.169 as permitted sender) Received: from [209.85.212.169] (HELO mail-wi0-f169.google.com) (209.85.212.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Nov 2013 03:21:59 +0000 Received: by mail-wi0-f169.google.com with SMTP id hi5so1918910wib.4 for ; Thu, 14 Nov 2013 19:21:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Q8i05y/Jj81J4JqoZ3Cp/MTLT7AeVUTyB+94EJcc6/c=; b=NrsZYUV4KGVBXk0s3Kz1BbJmdxpFyHTKvBERIpn1l5X0DTOtHk/5M1NOqz7vJRKdQ5 IBHxuScB9LGIocp+0TBZTAoWNWQlT9ziby04CJbQdWarOKkqFbPrDJGOpI1uORGh2C1g nq/jXr19Jlhsju5x8kXBL/E4dX16ve9iivIC3noI4ryQxiZPlDJTMIMqotXXsOHAkGmh tGcJBIhuPFEWQXWPBJOe0kPYzbslw4iW+5vxCivQutzumrzeD2HvlEtSU2ULzb45o/IC X596zZn/sOQdEx6cG8NzkOE3qQJ7rKpCKRi3sGpAytTSBX/N4us7HdpaUQdnUr28PKev 1fIg== MIME-Version: 1.0 X-Received: by 10.194.122.99 with SMTP id lr3mr4849405wjb.21.1384485699741; Thu, 14 Nov 2013 19:21:39 -0800 (PST) Received: by 10.217.48.9 with HTTP; Thu, 14 Nov 2013 19:21:39 -0800 (PST) In-Reply-To: References: <5004AF3F-BFC0-4845-A175-EC00FA133B29@gmail.com> Date: Fri, 15 Nov 2013 08:51:39 +0530 Message-ID: Subject: Re: Workflow monitoring in Client API From: Nipuni Piyabasi Perera To: Airavata Dev Content-Type: multipart/alternative; boundary=089e011779b5546db604eb2eb257 X-Virus-Checked: Checked by ClamAV on apache.org --089e011779b5546db604eb2eb257 Content-Type: text/plain; charset=ISO-8859-1 Hi, Given workflow name and its inputs, I am receiving the experiment id with, String experimentId =airavataAPI.getExecutionManager().runExperiment(workflowId, workflowInputs); Then start monitoring here, MonitorListener monitorListener = new MonitorListener(); Monitor experimentMonitor = airavataAPI.getExecutionManager().getExperimentMonitor(experimentId, monitorListener); log.info("Started the Workflow monitor"); This code executes and prints the log message. But this does not print log messages inside notify() method in "MonitorListner" class public void notify(EventDataRepository eventDataRepo, EventData eventData) { log.info("ExperimentID: " + eventData.getExperimentID()); log.info("Message: " + eventData.getMessage()); } On Fri, Nov 15, 2013 at 8:25 AM, Saminda Wijeratne wrote: > hi Nipuni, > When the experiment starts the events are generated at the server side > regardless whether anyone starts monitoring or not. By startMonitoring() at > the client side it will subscribe to those generated events. Server will > send the client a copy of those events. > > How are you passing your listener to the API? Can you illustrate what you > are doing in code? > > > On Thu, Nov 14, 2013 at 9:14 PM, Nipuni Piyabasi Perera < > nipuni880917@gmail.com> wrote: > >> Hi, >> >> To monitor workflow execution, I have registered a listener with monitor >> as in the sample code here[1]. My Listener class [2] should call notify() >> method if there is any events generated while workflow execution. But it >> does not call notify method. After "startMonitoring()" is called does it >> automatically generate events?. >> >> I am using Airavata 0.7 release. >> >> [1] https://svn.apache.org/repos/asf/airavata/trunk/samples/airavata-client/workflow-run/src/main/java/org/apache/airavata/client/samples/MonitorWorkflow.java >> >> >> [2] >> https://svn.apache.org/repos/asf/airavata/tags/airavata-0.7/samples/airavata-client/workflow-run/src/main/java/org/apache/airavata/client/samples/MonitorListener.java >> >> Thanks, >> Nipuni. >> >> >> On Wed, Aug 7, 2013 at 7:07 PM, Raminder Singh wrote: >> >>> Thanks for your interest in Airavata. You need not to poll. You can >>> register a listener with your monitor to get constant updates. Please look >>> into following class. >>> >>> >>> https://svn.apache.org/repos/asf/airavata/tags/airavata-0.7/samples/airavata-client/workflow-run/src/main/java/org/apache/airavata/client/samples/MonitorListener.java >>> >>> Thanks >>> Raminder >>> >>> On Aug 7, 2013, at 1:22 AM, Nipuni Piyabasi Perera < >>> nipuni880917@gmail.com> wrote: >>> >>> >>> Hi, >>> >>> I am implementing Airavata client API and I need to monitor running >>> workflow status. I have noticed that a "Monitor" can be accessed via >>> "ExecutionManager" [1], and it provides startMonitoring() and >>> stopMonitoring() methods. >>> I need to clarify whether it allows to display workflow status >>> continuously or does it need poll to view status. >>> >>> [1] >>> https://svn.apache.org/repos/asf/airavata/tags/airavata-0.7/samples/airavata-client/workflow-run/src/main/java/org/apache/airavata/client/samples/MonitorWorkflow.java >>> >>> Thanks, >>> Nipuni >>> -- >>> Nipuni Piyabasi Perera >>> Undergraduate >>> Department of Computer Science And Engineering >>> University of Moratuwa >>> Sri Lanka >>> >>> >>> >> >> >> -- >> Nipuni Piyabasi Perera >> Undergraduate >> Department of Computer Science And Engineering >> University of Moratuwa >> Sri Lanka >> > > -- Nipuni Piyabasi Perera Undergraduate Department of Computer Science And Engineering University of Moratuwa Sri Lanka --089e011779b5546db604eb2eb257 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Given workflow name and its inputs, I am r= eceiving the experiment id with,

=A0=A0=A0=A0=A0=A0=A0=A0=A0 String experime= ntId =3DairavataAPI.getExecutionManager().runExperiment(workflowId, workflo= wInputs);

Then start monitoring here,

=A0=A0=A0=A0=A0=A0= =A0=A0=A0 MonitorListener monitorListener =3D new MonitorListener();
=A0= =A0=A0=A0=A0=A0=A0=A0=A0 Monitor experimentMonitor =3D airavataAPI.getExecu= tionManager().getExperimentMonitor(experimentId,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 monitorListener);
=A0=A0= =A0=A0=A0=A0=A0=A0=A0 log.info("Starte= d the Workflow monitor");

This code executes and prints the log message. But this does not print log=20 messages inside notify() method in "MonitorListner" class

= 
pub=
lic void notify(EventDataRepository eventDataRepo, EventData eventData) {
        log.info("ExperimentID: "=
 + eventData.getExperimentID());
        log.info("Message: " + ev=
entData.getMessage());
    }


On Fri, Nov 15, 2013 at 8:25 AM, Saminda Wijeratne <sam= indaw@gmail.com> wrote:
hi Nipuni,
When the experiment starts the events are generated at the server side r= egardless whether anyone starts monitoring or not. By startMonitoring() at = the client side it will subscribe to those generated events. Server will se= nd the client a copy of those events.

How are you passing your listener to the API? Can you illustrate = what you are doing in code?


On Thu, Nov= 14, 2013 at 9:14 PM, Nipuni Piyabasi Perera <nipuni880917@gmail.com= > wrote:
Hi,

= To monitor workflow execution, I have=20 registered a listener with monitor as in the sample code here[1]. My=20 Listener class [2] should call notify() method if there is any events=20 generated while workflow execution. But it does not call notify method.=20 After "startMonitoring()" is called does it automatically generat= e=20 events?.

I am using Airavata 0.7 release.

[1] https://svn.apache.org/repos/asf/airavata/= trunk/samples/airavata-client/workflow-run/src/main/java/org/apache/airavat= a/client/samples/MonitorWorkflow.java

[2] https://svn= .apache.org/repos/asf/airavata/tags/airavata-0.7/samples/airavata-client/wo= rkflow-run/src/main/java/org/apache/airavata/client/samples/MonitorListener= .java

Thanks,
Nipuni.


On Wed, Aug 7, 2013 at 7:07 PM, = Raminder Singh <raminderjsingh@gmail.com> wrote:
Thanks f= or your interest in Airavata. You need not to poll. You can register a list= ener with your monitor to get constant updates. Please look into following = class.=A0


Thanks
Raminder=
=A0
On Aug 7, 2013, at 1:2= 2 AM, Nipuni Piyabasi Perera <nipuni880917@gmail.com> wrote:


Hi,

I am implementing Airavata client API and = I need to monitor running workflow status. I have noticed that a "Moni= tor" can be accessed via=A0 "ExecutionManager" [1], and it p= rovides startMonitoring() and stopMonitoring() methods.
I need to clarify whether it allows to display workflow status continuously= or does it need poll to view status.

[1] https://svn.apache.org/repos/asf/airavata/tags/airavat= a-0.7/samples/airavata-client/workflow-run/src/main/java/org/apache/airavat= a/client/samples/MonitorWorkflow.java

Thanks,
Nipuni
--
Nipuni Piyabasi Per= era
Undergraduate
Department of Computer Scien= ce And Engineering
University of Moratuwa
Sri Lanka



--
Nipuni Piyabasi PereraUndergraduate
Department of Computer Science And Engineer= ing
University of Moratuwa
Sri Lanka




--
= Nipuni Piyabasi Perera
Undergraduate
Departmen= t of Computer Science And Engineering
University of Moratuwa
Sri Lanka
--089e011779b5546db604eb2eb257--