Return-Path: Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: (qmail 76610 invoked from network); 2 Apr 2010 02:53:56 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Apr 2010 02:53:56 -0000 Received: (qmail 98932 invoked by uid 500); 2 Apr 2010 02:53:56 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 98602 invoked by uid 500); 2 Apr 2010 02:53:55 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 98592 invoked by uid 99); 2 Apr 2010 02:53:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Apr 2010 02:53:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of samisa.abeysinghe@gmail.com designates 209.85.223.183 as permitted sender) Received: from [209.85.223.183] (HELO mail-iw0-f183.google.com) (209.85.223.183) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Apr 2010 02:53:48 +0000 Received: by iwn13 with SMTP id 13so212344iwn.13 for ; Thu, 01 Apr 2010 19:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=8sBWyiouBKCAQv/ggSb3fu7l9zrxVs90XjMxiHhP+dY=; b=aq6J+DXhywCFUv8Jk7mqnp40qF2+zdORvpEVS11f1EBape0oINBmjo5PbrmMRVsf7S QgJEwuI8ZH30/q1R17AMuh8558mr/KmTzHBiAaTw8qIymyoDBt+TlUug7Tv3LgDqRh86 0BMfwlhMDht6l1AEW7AoolzDLMtc/CCtOxo2M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SJIEydXopLspjSnbUWATeLMPdPZljekk61xPYRSFvyWK1RSnOWMWGJi2No+4tE/pBk ci3GRZPvz7sa3wg53qn+OjbD2dv+DR7sOW0euzRj9ZrHmXVUEiCAE6yw6NPc1McVLoiX wa/UC5fsQB5WElFZ8BI5meTAyVlolaG9XUuHQ= MIME-Version: 1.0 Received: by 10.231.153.137 with HTTP; Thu, 1 Apr 2010 19:53:27 -0700 (PDT) In-Reply-To: References: <3054da0f1003241438n62153ab8hf7201a18d98a58c4@mail.gmail.com> <3054da0f1003241503x4805a81bt10c2b2f44300bc0b@mail.gmail.com> Date: Fri, 2 Apr 2010 08:23:27 +0530 Received: by 10.231.147.148 with SMTP id l20mr540208ibv.77.1270176807100; Thu, 01 Apr 2010 19:53:27 -0700 (PDT) Message-ID: Subject: Re: [GSoC Project Proposal] Distributed TCP Monitor From: Samisa Abeysinghe To: java-dev@axis.apache.org Content-Type: multipart/alternative; boundary=0016e6498a5c63a04d0483381578 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6498a5c63a04d0483381578 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Apr 2, 2010 at 7:12 AM, Srinath Perera wrote: > Hi nilupa; > > IMO this thread has more than one concept. Initially, the version I > discussed with you is more of a message monitoring tool, which allow > an user to see which message goes through where in the system. It is > purely used for debugging services only, and a actually it distributed > TCP monitor that helps people debug their distributed application. > Features I had in my mind was to > > 1. Ability to turn on/off message interception > 2. When tuned on, it show the system in a UI and let me see all > messages went through each link I selected. > 3. If messages have a some ID that identify a message sequence, it > should let me select a message and find sequence that generated/ lead > to that message. > > Basically, as I mentioned before, it is debugging tool and not a > monitoring tool. > If it is a debugging tool, that is going to be useful. Samisa... > > Then, there is a BAM/System monitoring aspect we heavily discussed in > this thread, which is used to monitor a running system. IMHO they are > different,yet very useful. However, they are targeted at two audiences > and you should not do half of each. > > Personlly, I am interested in both topics, and willing to > mentor/co-mentor either, however, IMO it two projects, not one. > > Thanks > Srinath > > > > On Fri, Apr 2, 2010 at 12:17 AM, Andreas Veithen > wrote: > > Probably the right answer to this question is: none. Why would the > > individual nodes intercepting the messages use publish/subscribe? They > > should all send them to a central place (or back to the sender of the > > original request). > > > > Andreas > > > > On Wed, Mar 31, 2010 at 16:51, Samisa Abeysinghe > > wrote: > >>> Then we can take this to next level by adding this module to all > >>> services in a system , configuring modules to send all collected > >>> messages to a pub/sub channel, and subscribing to those messages via a > >>> UI, and depicting those messages through a UI. > >> > >> What pub/sub model do you plan to use? WS-Eventing? > >> > >> Samisa... > >> -- > >> blog: http://samisa-abeysinghe.blogspot.com/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > > For additional commands, e-mail: java-dev-help@axis.apache.org > > > > > > > > -- > ============================ > Srinath Perera, Ph.D. > WSO2 Inc. http://wso2.com > Blog: http://srinathsview.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > For additional commands, e-mail: java-dev-help@axis.apache.org > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://wso2.com/ - "lean . enterprise . middleware" --0016e6498a5c63a04d0483381578 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Apr 2, 2010 at 7:12 AM, Srinath = Perera <hemapani= @gmail.com> wrote:
Hi nilupa;

IMO this thread has more than one concept. Initially, the version I
discussed with you is more of a message monitoring tool, which allow
an user to see which message goes through where in the system. It is
purely used for debugging services only, and a actually it distributed
TCP monitor that helps people debug their distributed application.
Features I had in my mind was to

1. Ability to turn on/off message interception
2. When tuned on, it show the system in a UI and let me see all
messages went through each link I selected.
3. If messages have a some ID that identify a message sequence, it
should let me select a message and find sequence that generated/ lead
to that message.

Basically, as I mentioned before, it is debugging tool and not a
monitoring tool.

If it is a debugging t= ool, that is going to be useful.=A0

Samisa...
=A0

Then, there is a BAM/System monitoring aspect we heavily discussed in
this thread, which is used to monitor a running system. IMHO they are
different,yet very useful. However, they are targeted at two audiences
and you should not do half of each.

Personlly, I am interested in both topics, and willing to
mentor/co-mentor either, however, IMO it two projects, not one.

Thanks
Srinath



On Fri, Apr 2, 2010 at 12:17 AM, Andreas Veithen
<andreas.= veithen@gmail.com> wrote:
> Probably the right answer to t= his question is: none. Why would the
> individual nodes intercepting the messages use publish/subscribe? They=
> should all send them to a central place (or back to the sender of the<= br> > original request).
>
> Andreas
>
> On Wed, Mar 31, 2010 at 16:51, Samisa Abeysinghe
> <samisa.abeysinghe@g= mail.com> wrote:
>>> Then we can take this to next level by adding this module to a= ll
>>> services in a system , configuring modules to send all collect= ed
>>> messages to a pub/sub channel, and subscribing to those messag= es via a
>>> UI, and depicting those messages through a UI.
>>
>> What pub/sub model do you plan to use? WS-Eventing?
>>
>> Samisa...
>> --
>> blog:=A0http://samisa-abeysinghe.blogspot.com/
>
> ---------------------------------------------------------------------<= br> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>



--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
Srinath Perera, Ph.D.
=A0 WSO2 Inc. http://wso2.co= m
=A0 Blog: http://srinathsview.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

--=A0
Samisa Abeysinghe=A0
Dire= ctor, Engineering - WSO2 Inc.

http://ws= o2.com/ - "lean . enterprise . middleware"


--0016e6498a5c63a04d0483381578--