activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Commented] (AMQ-3876) WireTap of TransportConnector messages for diagnostic purposes
Date Thu, 14 Jun 2012 10:22:42 GMT


Gary Tully commented on AMQ-3876:

There is some overlap with trace=true&startLogging=false&dyanmicManagement=true tcp
transport options.

These allow u to enable (via jmx) trace logging on a connection, of all of the operwire commands.

Accessing the log remotely I guess is still a difficulty but a using a remote appender would
sort that.

did you find some limitations with the existing TcpTransport trace support?

> WireTap of TransportConnector messages for diagnostic purposes
> --------------------------------------------------------------
>                 Key: AMQ-3876
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: Arthur Naseef
>            Priority: Minor
>         Attachments:, WiretapPrototype1.patch
> Being able to tap into the flow of messages on a TransportConnection would greatly help
with diagnosing problems such as complaints from clients that they are not receiving messages.
> Think "tcpdump" for broker traffic.
> A rough, working prototype will be attached.
> The idea in the prototype is a new Connector on the BrokerService which does the following:
> * accepts connections from a wire-tap tool (application)
> * accepts a request to tap a specific TransportConnection
> * adds a tap to the TransportConnection (requires change to TransportConnection)
> * sends a copy of every command sent over the connection, via the {{oneway}} call, to
the tap
> After posting the prototype, I'll post wish-list items.
> If someone with more knowledge and background working with connectors can pick this up,
that would be great.  Otherwise, I'll plan to implement it, looking for any advice.  For example,
one concern is that the tap should prefer to drop content rather than either (a) use large
amounts of resources to buffer them, or (b) in any way impacting the normal flow on the TransportConnection.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message