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/NETCONF-133 netconf <p>Tested on: stable/beryllium<br/> Caught by: Netconf MDSAL Northbound suite</p> <p>After user sends invalid data to the "modules" node of ODL's NETCONF configutation and after that request errors out (uncleanly, see <a href="https://jira.opendaylight.org/browse/NETCONF-132" title="Incorrect error response after user sends invalid data" class="issue-link" data-issue-key="NETCONF-132"><del>NETCONF-132</del></a>), all other operations in that session fail with</p> <p>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;<br/> &lt;rpc-reply message-id="6" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;<br/> &lt;rpc-error&gt;<br/> &lt;error-type&gt;application&lt;/error-type&gt;<br/> &lt;error-tag&gt;operation-failed&lt;/error-tag&gt;<br/> &lt;error-severity&gt;error&lt;/error-severity&gt;<br/> &lt;error-message&gt;Unexpected error&lt;/error-message&gt;<br/> &lt;error-info&gt;<br/> &lt;error&gt;java.lang.IllegalStateException: Transaction DOM-31 is no longer running&lt;/error&gt;<br/> &lt;/error-info&gt;<br/> &lt;/rpc-error&gt;<br/> &lt;/rpc-reply&gt;</p> <p>(the "DOM-31" in the &lt;error&gt; element can vary).</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-133

"Transaction ... is no longer running" after user sends invalid data.

Bug Resolved Done Andrej Mak Jozef Behran Tue, 26 Jan 2016 10:07:05 +0000 Fri, 15 Mar 2019 22:22:19 +0000 Fri, 12 Feb 2016 09:01:44 +0000 netconf 0 3 <p>Is this still present?</p> <p>The "invalid data" are for example the following file in Gerrit:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/27672/19/csit/variables/netconf/MDSAL/merge-multiple-replace-request.msg" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/27672/19/csit/variables/netconf/MDSAL/merge-multiple-replace-request.msg</a></p> <p>It contains a complete request which, when sent to ODL, will trigger the bug.</p> <p>The bug is still there as of today. A Sandbox test run just finished on build 3866 and the bug can still be seen there.</p> <p>Is the workaround just to start a new session? I ask since this sounds pretty bad, but I am not sure if its the type of thing we should raise to a critical/blocker level.</p> <p>Thanks for your feedback, Jozef.</p> <p>New session should fix it, the problem is that the failure of the commit is not correctly handled.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34089/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34089/</a></p> Development External issue ID 5096 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01wnr: