OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [ODLPARENT-177] Modification of etc/org.ops4j.pax.web.cfg at runtime renders most of deployed servlets unusable https://jira.opendaylight.org/browse/ODLPARENT-177 odlparent <p>Not sure if this project is right place to report this issue, so please move if necessary.</p> <p>Following procedure used to work until Fluorine:</p> <ol> <li>install odl-restconf-all</li> <li>after successfully started, modify etc/org.ops4j.pax.web.cfg (for example change HTTPs settings)</li> <li>Wait for change to propagate</li> </ol> <p>Updating etc/org.ops4j.pax.web.cfg triggers reload of some pax-web bundles which results in existing servlets being undeployed:</p> <p> </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>opendaylight-user@root&gt;http:list ID  │ Servlet            │ Servlet-Name                     │ State       │ Alias               │ Url ────┼────────────────────┼──────────────────────────────────┼─────────────┼─────────────────────┼──────────────────────────────────── 188 │ JolokiaServlet     │ ServletModel-2                   │ Undeployed  │ /jolokia            │ [/jolokia/*] 237 │ DiagStatusServlet  │ ServletModel-5                   │ Undeployed  │ /diagstatus         │ [/diagstatus/*] 304 │ ResourceServlet    │ /apidoc/explorer:/explorer       │ Undeployed  │ /apidoc/explorer    │ [/apidoc/explorer/*] 198 │ OAuth2TokenServlet │ ServletModel-10                  │ Undeployed  │ /oauth2             │ [/oauth2/*] 304 │ ServletContainer   │ ServletContainer                 │ Undeployed  │                     │ [/apidoc/apis/*, /apidoc/18/apis/*] 198 │ MoonTokenEndpoint  │ ServletModel-8                   │ Undeployed  │ /moon               │ [/moon/*] 304 │ ResourceServlet    │ /apidoc/18/explorer:/18/explorer │ Undeployed  │ /apidoc/18/explorer │ [/apidoc/18/explorer/*] 188 │ JolokiaServlet     │ ServletModel-38                  │ Deployed    │ /jolokia            │ [/jolokia/*] opendaylight-user@root&gt;</pre> </div></div> <p> </p> <p>Now any restconf query will return HTTP404.</p> <p>Fluorine-SR1</p> ODLPARENT-177 Modification of etc/org.ops4j.pax.web.cfg at runtime renders most of deployed servlets unusable Bug Medium Open Unresolved Unassigned Richard Kosegi Tue, 27 Nov 2018 16:33:42 +0000 Mon, 6 Feb 2023 22:03:45 +0000 11.0.4 Karaf 0 3 <p>This affects servlets across projects - seems like a general karaf/pax web issue so seems appropriate for odlparent.</p> <p>I suspect this is caused by blueprint being used to inject the servlets and the service going away, losing registrations and BP not restating</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rkosegi" class="user-hover" rel="rkosegi">rkosegi</a> is this still repreducible? anmd if so, can you attach karaf.log?</p> <p>Hi Robert, I just tried with Chlorine-SR2 (0.17.2) and it's still reproducible using same steps.</p> <p>Karaf log is attached, modification of config file occurred at timestamp "2023-02-02T18:03:15,361".</p> <p>Then I hit apidocs at "2023-02-02T18:03:24,315" and got bunch of stacktraces in log</p> <p>The logs seem to indicate the /apidoc endpoint was refreshed and as such, it should not be affected by pax-web configuration: we are using HTTP Whiteboard, hence if pax-web is refreshed, it should just pick up our services from OSGi SR and re-publish them to whatever underlay.</p> <p>This does not seem to be the case, hence this needs a deeper analysis to determine whether we (odlparent/netconf) should do something differently, or if pax-web needs to fix something. As the exceptions are triggered when accessing the port, it feels like it is a pax-web problem – but we need the smoking gun...</p> Development Rank 0|i03l0v: