-
Sub-task
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
initially, just add the call. we can save the results to a file and log them like we do with other
things like packet traces, exceptions, etc.
but hopefully, at some point, we can fail if the output is non-empty, which probably
indicates some leftover unfinished (aka leaking) transactions
- blocks
-
NETVIRT-878 CSIT should help to detect possible memory leaks leading to OOM related to non-closed transactions (and tx chains) early
- In Progress
-
MDSAL-213 Serializing DataObject to JSON causes frozen class exception
- Resolved
- is blocked by
-
CONTROLLER-1765 trace:transactions should suppress false TransactionChain positives, by white list, or showing only x2+ ?
- Resolved
-
NETVIRT-1296 Transaction leak in VpnOpStatusListener
- Resolved
-
CONTROLLER-1832 Transaction Trace tool wiring creates second BindingToNormalizedNodeCodec
- Resolved
-
CONTROLLER-1834 Transaction Trace tool wiring for ping-pong DataBroker is wrong
- Resolved
-
NETVIRT-1295 Transaction leak in ExternalRoutersListener
- Resolved
-
OPNFLWPLUG-1043 Transaction leak in ForwardingRulesManagerImpl (ReadOnly)
- Resolved