-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
This is encountered in testing, when a ClientBackedTransactionChain is closed, it emits a set of warnings:
2019-02-19T18:22:10,648 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-34-0 2019-02-19T18:22:10,648 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-29-0 2019-02-19T18:22:10,648 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-32-0 2019-02-19T18:22:10,649 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-33-0 2019-02-19T18:22:10,649 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-30-0 2019-02-19T18:22:10,650 | WARN | Framework stop | ClientBackedTransactionChain | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.10.0.SNAPSHOT | Aborting unclosed transaction member-3-datastore-operational-fe-2-chn-1-txn-31-0
These lack a context which would point towards where the transaction chain lives. Moreover it seems these can potentially include previous transactions, as those are recorded too.