axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: [GSoC Project Proposal] Distributed TCP Monitor
Date Sat, 27 Mar 2010 16:40:28 GMT
Personally, I think that the added value of extending the SOAP monitor
module to collect messages in a central place is too limited to
attract enough interest from the user community, so that it will be
difficult to ensure the evolution of such a project in the future.
However, what many people are looking for is a tool that allows to
track the flow of a message through a distributed system, or more
generally to track the sequence of events triggered by a given input
message (sort of end-to-end transaction monitoring).

On Wed, Mar 24, 2010 at 23:03, nilupa bandara <> wrote:
> Hello,
> I am graduate student at Politecnica de Madrid and I am thinking of
> proposing a GSoC project this summer. I would like to take project
> "Distribute TCP Monitor" descried[1] which is very interesting and
> also should be helpful to any Java developer using Apache Axis2 Web
> services middleware. I will submit more detailed proposal later. I
> would really like to hear any feedback from you. Any suggestions or
> features that you would like to see in a "Distributed TCP Monitor" are
> most welcome.
> Best Regards,
> Nilupa Bandara
> [1]
> Distributed TCP monitor
> To use TCP monitor we have to tweak the endpoints, which is bit hard
> sometimes (e.g. two channels Async case for Axis2). We can solve the
> problem by writing a Axis2 module (Handler) that intercept messages
> comes in and goes out of a Axis2 server and send to a UI (via a
> pub/sub channel or a message Box e.g. ) or record them so user can
> pull those messages. Also, we can do something to turn the module on
> and off remotely, so users can have his module deployed, but turn it
> on only when they want to debug the system.
> 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. Then users have a
> TCPMon for a whole system.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message