OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [OPNFLWPLUG-935] TransactionChain created in OperationProcessor.<init> line 36 is never closed https://jira.opendaylight.org/browse/OPNFLWPLUG-935 OpenFlowPlugin <p>As found in see <a href="https://jira.opendaylight.org/browse/CONTROLLER-1760" title="Tooling to find the real root cause culprit of memory leaks related to non-closed transactions (and tx chains)" class="issue-link" data-issue-key="CONTROLLER-1760"><del>CONTROLLER-1760</del></a> motivated by <a href="https://jira.opendaylight.org/browse/CONTROLLER-1756" title="OOM due to huge Map in ShardDataTree" class="issue-link" data-issue-key="CONTROLLER-1756"><del>CONTROLLER-1756</del></a>:</p> <p>TransactionChain created in OperationProcessor.&lt;init&gt; line 36 is never closed</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-935 TransactionChain created in OperationProcessor.<init> line 36 is never closed Bug Resolved Duplicate Jozef Bacigal Michael Vorburger Tue, 29 Aug 2017 22:06:06 +0000 Mon, 27 Sep 2021 09:02:05 +0000 Wed, 6 Sep 2017 17:19:45 +0000 General 0 5 <p>Any thoughts Tomas or someone?</p> <p>FYI: Since opening this bug (and others like it) I've understood that this is not yet necessarily proof of a real problem - see e.g. discussion in <a href="https://jira.opendaylight.org/browse/NETCONF-462" title="TransactionChain created in RestConnectorProvider.start line 87 is never closed" class="issue-link" data-issue-key="NETCONF-462"><del>NETCONF-462</del></a>:</p> <p>Basically if this OperationProcessor (which I've absolutely no idea what it is, obviously) has a lifecycle of application scope, that is if its an object you (Blueprint) creates on boot, with a single instance which stays alive for the entire ODL lifetime, where you create ONE (and always only ever one, never more) TransactionChain in there, and you are sure that under load you are not creating more TransactionChain instances which are never closed, then this was a false positive - please feel free to close this as RESOLVED INVALID, if you are sure that this it the case here (like in <a href="https://jira.opendaylight.org/browse/NETCONF-462" title="TransactionChain created in RestConnectorProvider.start line 87 is never closed" class="issue-link" data-issue-key="NETCONF-462"><del>NETCONF-462</del></a>).</p> <p>Also, I'll see if the <a href="https://jira.opendaylight.org/browse/CONTROLLER-1760" title="Tooling to find the real root cause culprit of memory leaks related to non-closed transactions (and tx chains)" class="issue-link" data-issue-key="CONTROLLER-1760"><del>CONTROLLER-1760</del></a> tool could perhaps be made a bit smarter, and would welcome feedback &amp; thoughts about this in <a href="https://jira.opendaylight.org/browse/CONTROLLER-1765" title="trace:transactions should suppress false TransactionChain positives, by white list, or showing only x2+ ?" class="issue-link" data-issue-key="CONTROLLER-1765"><del>CONTROLLER-1765</del></a>.</p> <p>Dupe to <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-933" title="IllegalStateException: Attempted to close chain with outstanding transaction PingPongTransaction at org.opendaylight.openflowplugin.impl.device.TransactionChainManager.createTxChain" class="issue-link" data-issue-key="OPNFLWPLUG-933"><del>OPNFLWPLUG-933</del></a> to KISS &amp; avoid general confusion.</p> Blocks CONTROLLER-1756 NETVIRT-883 Duplicate OPNFLWPLUG-933 Development External issue ID 9071 External issue URL Rank 0|i0347z: