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-315 netconf <p>when locating a netconf problem, the detail of netconf message usually should be printed</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-315

Add print in debug level when handle and send Netconf messages

Bug Resolved Cannot Reproduce Unassigned wang chao Mon, 14 Nov 2016 11:28:07 +0000 Fri, 15 Mar 2019 22:22:33 +0000 Mon, 24 Apr 2017 14:30:15 +0000 netconf 0 2 <p>Hello Wang,</p> <p>The messages seem to be already logged: see <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L291" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L291</a></p> <p>(In reply to Alexis de Talhouët from comment #1)<br/> &gt; Hello Wang,<br/> &gt; <br/> &gt; The messages seem to be already logged: see<br/> &gt; <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-</a><br/> &gt; connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/<br/> &gt; listener/NetconfDeviceCommunicator.java#L291</p> <p>I have seen this print, but it only prints the netconf message when rpc is error. In my print, I also want to see the netconf message in the correct situation.</p> <p>Wang,</p> <p>In the case the message is correct, the log that I linked above will be display: <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L291" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L291</a></p> <p>If the message is incorrect, it will be logged here: <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L280-L282" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/listener/NetconfDeviceCommunicator.java#L280-L282</a></p> <p>Both case are covered, I just tried them.</p> <p>(In reply to Alexis de Talhouët from comment #3)<br/> &gt; Wang,<br/> &gt; <br/> &gt; In the case the message is correct, the log that I linked above will be<br/> &gt; display:<br/> &gt; <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-</a><br/> &gt; connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/<br/> &gt; listener/NetconfDeviceCommunicator.java#L291<br/> &gt; <br/> &gt; If the message is incorrect, it will be logged here:<br/> &gt; <a href="https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/master/netconf/sal-netconf-</a><br/> &gt; connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/<br/> &gt; listener/NetconfDeviceCommunicator.java#L280-L282<br/> &gt; <br/> &gt; Both case are covered, I just tried them.</p> <p>The message in NetconfDeviceCommunicator.java and AbstractNetconfSession.java should be different. Besides, the log level is trace in NetconfDeviceCommunicator, in daily job, you seldomly set log level to trace, because it will print too much message.</p> <p>Messages are already logged in debug, trace logs only include additional information.</p> Development External issue ID 7173 External issue URL Rank 0|i01xs7: