The org.opendaylight.controller.md.sal.trace.dom.impl.TracingBroker JavaDoc says that one can add the mdsal-trace-features to the POM of a project's Karaf distribution (e.g. as done in https://git.opendaylight.org/gerrit/#/c/62403/ for netvirt) and that one should be able to then just do, first:
opendaylight-user@root>feature:install odl-mdsal-trace followed by (after!) then any other regular feature, such as: opendaylight-user@root>feature:install odl-netvirt-openstack
and that this would enable the TracingDOMDataBroker. However, on a current master this does not work anymore, presumably following an impact of the Karaf 4 migration which causes wrong feature/bundle reloads which did not happen before, and the e.g. odl-netvirt-openstack installation fails with:
Exception in thread "config-blank-txn-0" java.lang.IllegalStateException: Error while copying old configuration from ModuleInternalInfo [name=ModuleIdentifier{factoryName='distributed-operational-datastore-provider', instanceName='distributed-operational-store-module'}] to org.opendaylight.controller.config.yang.config.distributed_datastore_provider.DistributedOperationalDataStoreProviderModuleFactory@9897f5a Caused by: java.lang.ClassCastException: org.opendaylight.controller.config.yang.config.distributed_datastore_provider.OperationalProperties cannot be cast to org.opendaylight.controller.config.yang.config.distributed_datastore_provider.OperationalProperties
Resolving this is a pre-req. for CONTROLLER-1760 (which is req. for CONTROLLER-1756).
- 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
-
CONTROLLER-1760 Tooling to find the real root cause culprit of memory leaks related to non-closed transactions (and tx chains)
- Resolved
-
ODLPARENT-110 [Karaf 4] Avoid bundle refreshes
- Resolved
- is blocked by
-
ODLPARENT-132 odlparent 2.0.5 depends on servlet-api/3.0.1, whereas Karaf 4 depends on /3.1.0
- Resolved