https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1792 controller <p>Seeing uncaught listener thread exceptions in the stdout of the JVM</p> <p><a href="https://gist.github.com/smalleni/f896c79a388779ed1f7d82d795f85e05" class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/smalleni/f896c79a388779ed1f7d82d795f85e05</a></p> CONTROLLER-1792

IllegalStateException: Illegal state - listener for org.opendaylight.controller.md.sal.trace.dom.impl.TracingTransactionChain@... was invoked for incorrect chain org.opendaylight.controller.cluster.databroker.DOMBrokerTransactionChain@...

Bug Medium Resolved Done Michael Vorburger Sai Sindhur Malleni Fri, 17 Nov 2017 17:02:46 +0000 Fri, 24 Nov 2017 13:15:50 +0000 Fri, 24 Nov 2017 13:15:50 +0000 0 2 <p>&gt; <a href="https://gist.github.com/smalleni/f896c79a388779ed1f7d82d795f85e05" class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/smalleni/f896c79a388779ed1f7d82d795f85e05</a></p> <p>attached as gistfile1.txt so that its JIRA indexed... </p> <p><a href="https://jira.opendaylight.org/browse/CONTROLLER-1793" title="Exceptions in listener threads are going to stdout instead of karaf.log" class="issue-link" data-issue-key="CONTROLLER-1793"><del>MDSAL-297</del></a> will make these exceptions go into ODL log instead STDOUT, this issue is about fixing what is causing them.</p> <p>The trouble is that these exception do not contain the "origin" of what chains they are about (somewhat similar issue to <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>).</p> <p>More importantly, I do not yet understand what problem these exceptions are signaling.</p> <p>This IllegalStateException is thrown at org.opendaylight.controller.md.sal.binding.impl.BindingDOMTransactionChainAdapter.DelegateChainListener.onTransactionChainFailed().</p> <p>I missed on the first look last week that this is related to the TracingTransactionChain, which is our stuff for the trace:transaction Tx leak detection for OOM prevention; so the good news is this ONLY happens with <tt>feature:install odl-mdsal-trace</tt> (so it's not a "real" problem affecting production), but the bad news is we're finding here trace:transactions has this side-effect, when it was supposed to be transparent... even though AFAIK it's not causing any real harm. </p> <p>The TracingTransactionChain is just a wrapper around the DOMBrokerTransactionChain, but it fails the equals() check in that onTransactionChainFailed method. Perhaps that shouldn't be an equals, but... what?</p> <p>I'm inclined to just close this as WONTFIX .. or do we need to find a way to "fix" this?</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/65808/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/65808/</a>, or something like it, will probably fix this actually.. </p> <p>Thank You to <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tpantelis" class="user-hover" rel="tpantelis">tpantelis</a> for pointing me in that direction!</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=smalleni" class="user-hover" rel="smalleni">smalleni</a> we expect this to be fixed now (but I've not reproduced and tested it); if you still see it, so closing; please just re-open.</p> Development Rank 0|i037vz: