[
https://issues.apache.org/jira/browse/DISPATCH-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992594#comment-16992594
]
Ganesh Murthy edited comment on DISPATCH-1514 at 12/10/19 8:51 PM:
-------------------------------------------------------------------
I added https://issues.apache.org/jira/browse/DISPATCH-1518 to address [~gsim]
's suggestion in the above comment. DISPATCH-1514 will only deal with the bug
mentioned in the Jira descrption.
was (Author: ganeshmurthy):
I added https://issues.apache.org/jira/browse/DISPATCH-1518 to address [~gsim]
's suggestion in the above comment. This Jira will only deal with the bug
mentioned in the Jira descrption.
> Dynamically turning on trace logging via qdmanage does not turn proton frame
> tracing 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
> Fix For: 1.10.0
>
>
> 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 proton trace logging on existing
> connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
