[
https://issues.apache.org/jira/browse/AMQ-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290289#comment-13290289
]
Arthur Naseef commented on AMQ-3876:
------------------------------------
To use the example:
* Build and use the updated version of ActiveMQ
* Run a broker
* Create a connection, that will be tapped, to the broker
* Locate the connetion "name" ({{netstat -an | grep 61616}} works well under
Linux)
* Run the tap tool (note this is incomplete and makes assumptions, including
that the broker is running on the same server as the tool):
{code}
java WireTap localhost 5500 /127.0.0.1:45001
{code}
> WireTap of TransportConnector messages for diagnostic purposes
> --------------------------------------------------------------
>
> Key: AMQ-3876
> URL: https://issues.apache.org/jira/browse/AMQ-3876
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Arthur Naseef
> Priority: Minor
> Attachments: WireTap.java, 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
