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-718 netconf <p>Current RESTCONF implementation is utterly blocking due to its declared interface towards JAX-RS. This can be fixed with use of @Suspended, so that the implementation properly composes MD-SAL operations and notifies JAX-RS when the result is done.</p> NETCONF-718

Switch to using asynchronous JAX-RS interface

Improvement High Confirmed Unresolved Unassigned Robert Varga pt Mon, 3 Aug 2020 09:49:46 +0000 Tue, 10 Oct 2023 12:42:40 +0000 7.0.0 restconf-nb 0 1 <p>We need parts of the patches introduced here, but overall this is getting a bit moot with adoption of <a href="https://github.com/eclipse/jetty.project/issues/8007" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/eclipse/jetty.project/issues/8007</a> – i.e. once we have Jetty 10. Once we have Java 21 (assuming Loom makes it there as production feature), we just need to make sure it is configured accordingly and then we can revert to sync interface.</p> <p>If this crops up and we still do not have above, the migration still makes sense to conserve threads.</p> <p>So <a href="https://openjdk.org/jeps/444" class="external-link" target="_blank" rel="nofollow noopener">JEP-444</a> is in Java 21, but our adoption quite some time away.<br/> That actually does not make this issue as moot as it would appear, as the async interface allows us to cleanly perform error mapping, e.g. not rely on ExceptionMapper and having RestconfDocumentedException be a proper checked exception.</p> <p>For reasons of sanity, we need to integrate putData()/postData() into RestconfStrategy first.</p> Blocks NETCONF-1125 NETCONF-1126 NETCONF-1155 Development Epic Link NETCONF-773 Rank 0|i03u7b: