[
https://issues.apache.org/jira/browse/DISPATCH-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990009#comment-16990009
]
Gordon Sim edited comment on DISPATCH-1514 at 12/6/19 5:34 PM:
---------------------------------------------------------------
It would be nice to be able to turn on tracing per connection, e.g. something
like `qdmanage update --type=connection id=897644 tracing=true`
That way you could benefit from protocol level tracing on connections of
interest as and when needed. Perhaps also there could be some way of specifying
a policy for connection tracing, e.g. all connections whose container id is
'foo' or who are connecting from 192.666.555.444 or similar.
was (Author: gsim):
It would be nice to be able to turn on tracing per connection, e.g. something
like qdmanage update --type=connection id=897644 tracing=true
> Dynamically turning on trace logging via qdmanage does not trace log on
> existing connections
> --------------------------------------------------------------------------------------------
>
> Key: DISPATCH-1514
> URL: https://issues.apache.org/jira/browse/DISPATCH-1514
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.9.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Priority: Major
>
> Steps to reproduce -
> # Start a router
> # Connect a sender and receiver to the router and let them send/receive
> message
> # While the sender and receiver are sending/receiving, use qdmanage to turn
> on trace logging - qdmanage update --type=log name=log/DEFAULT enable=trace+
> # Notice that the trace logging for the sender and receiver were not turned
> on,
> # Turning on trace logging must enable tracing on existing connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
