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/INFRAUTILS-37 infrautils <p><a href="https://jira.opendaylight.org/browse/INFRAUTILS-36" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 (NoSuchElementException) at acquireServiceStatusDetailed(DiagStatusServiceMBeanImpl.java:119)" class="issue-link" data-issue-key="INFRAUTILS-36"><del>INFRAUTILS-36</del></a> made me look more into the code in DiagStatusCommand, and I don't understand why on earth it uses JMX to call LOCAL code? I get the point of that code to get diagstatus from remote cluster members, but to query the local diagstatus, that seems... weird - we can, easily, just call the local service!</p> <p>I'll raise a change proposing this.</p> INFRAUTILS-37

diagstatus CLI should not to use JMX to obtain information from local node to avoid ConnectException on 127.0.0.1

Bug High Resolved Done Michael Vorburger Michael Vorburger Wed, 2 May 2018 10:51:01 +0000 Fri, 24 Aug 2018 10:51:03 +0000 Tue, 29 May 2018 13:10:26 +0000 Fluorine diagstatus 0 3 <p>The RMI Connector will not be involved, when DiagStatusCommand detects that 127.0.0.1 is self-address. So we should debug why 127.0.0.1 is not coming as self-address. If is it not coming, the proposed patch from Michael also will not solve the problem.</p> <p>This really (now, with the new log) is a functional Bug and no longer just a technical Enhancement idea.</p> <p>No, I got totally confused... as discussed on c/71662, my proposed technical enhancement will NOT fix the problem <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=jluhrsen" class="user-hover" rel="jluhrsen">jluhrsen</a> hit, because it does not do away with this code path - NB getRemoteStatusSummary() VS getLocalStatusSummary(). To avoid confusing others further, I propose that we keep this issue for the technical enhancement, and track the actual functional bug under a new <a href="https://jira.opendaylight.org/browse/INFRAUTILS-38" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 due to rmi.ConnectException: Connection refused to host: 127.0.0.1" class="issue-link" data-issue-key="INFRAUTILS-38"><del>INFRAUTILS-38</del></a>. I'll delete my previous comment above with the stack trace to avoid future confusion of this issue with the new <a href="https://jira.opendaylight.org/browse/INFRAUTILS-38" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 due to rmi.ConnectException: Connection refused to host: 127.0.0.1" class="issue-link" data-issue-key="INFRAUTILS-38"><del>INFRAUTILS-38</del></a>.</p> <p>I am not sure which Jira to comment on, this or <a href="https://jira.opendaylight.org/browse/INFRAUTILS-38" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 due to rmi.ConnectException: Connection refused to host: 127.0.0.1" class="issue-link" data-issue-key="INFRAUTILS-38"><del>INFRAUTILS-38</del></a> but something I just learned.</p> <p>in my <a href="https://git.opendaylight.org/gerrit/#/c/70220/" class="external-link" target="_blank" rel="nofollow noopener">patch</a> where I'm trying to do the status.getErrorCause().get() I will hit this problem<br/> where I get:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">Status retrieval JMX Operation failed <span class="code-keyword">for</span> node 127.0.0.1</pre> </div></div> <p>Ignoring the trace for now.</p> <p>NOTE: this is all manually and locally.</p> <p>When I remove that .get(), the problem goes away, so I'll get this:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">karaf@root()&gt; showsvcstatus Timestamp: Wed May 02 11:14:19 PDT 2018 Node IP Address: 127.0.0.1 <span class="code-object">System</span> is operational: <span class="code-keyword">true</span> <span class="code-object">System</span> ready state: ACTIVE OPENFLOW : OPERATIONAL Optional.empty karaf@root()&gt;</pre> </div></div> <p>So, maybe we can keep this <a href="https://jira.opendaylight.org/browse/INFRAUTILS-37" title="diagstatus CLI should not to use JMX to obtain information from local node to avoid ConnectException on 127.0.0.1" class="issue-link" data-issue-key="INFRAUTILS-37"><del>INFRAUTILS-37</del></a> as this specific issue and figure that out. However, the<br/> other problem we can track in <a href="https://jira.opendaylight.org/browse/INFRAUTILS-38" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 due to rmi.ConnectException: Connection refused to host: 127.0.0.1" class="issue-link" data-issue-key="INFRAUTILS-38"><del>INFRAUTILS-38</del></a> is maybe related, but also not because of the .get()<br/> issue. That is running a distro that does not have that change. I'll comment more in that jira.</p> <p>ok, so we can let this jira stay to track the work <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vorburger" class="user-hover" rel="vorburger">vorburger</a> is doing in <a href="https://git.opendaylight.org/gerrit/#/c/71662/" class="external-link" target="_blank" rel="nofollow noopener">71662</a>. I did cherry pick<br/> it locally to double check that it does <b>not</b> help me get past <a href="https://jira.opendaylight.org/browse/INFRAUTILS-36" title="showSvcStatus: Status retrieval JMX Operation failed for node 127.0.0.1 (NoSuchElementException) at acquireServiceStatusDetailed(DiagStatusServiceMBeanImpl.java:119)" class="issue-link" data-issue-key="INFRAUTILS-36"><del>INFRAUTILS-36</del></a>, so we still need that to<br/> chase down. I'll update that jira too.</p> Development Rank 0|i03e3r: