[DISPATCH-1514] Dynamically turning on trace logging via qdmanage does not turn proton frame tracing on existing connections

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.10.0
• Component/s: Container
• Assignee: Ganesh Murthy
• Reporter: Ganesh Murthy
• Created: 06/Dec/19 17:30
• Updated: 20/Dec/19 12:11
• Resolved: 11/Dec/19 21:08

Description

Steps to reproduce -

1. Start a router
2. Connect a sender and receiver to the router and let them send/receive message
3. While the sender and receiver are sending/receiving, use qdmanage to turn on  trace logging - qdmanage update --type=log name=log/DEFAULT enable=trace+
4. Notice that the trace logging for the sender and receiver were not turned on,
5. Turning on trace logging must enable proton trace logging on existing connections.

Issue Links

• links to: GitHub Pull Request #641