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/OPNFLWPLUG-694 OpenFlowPlugin <p>Stop instantiating new thread for echo after switch connected. Rather prepare threadpool while starting OFP and reuse threads.</p> <p> @Override<br/> public void onSwitchIdleEvent(final SwitchIdleEvent notification) {<br/> new Thread(new Runnable() {</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-694

OFP - Reuse Threads using ThreadPool in SystemNotificationListenerImpl.java

Bug Resolved Done Jozef Bacigal Jozef Slezák Thu, 19 May 2016 13:55:31 +0000 Mon, 27 Sep 2021 09:01:49 +0000 Tue, 21 Jun 2016 09:13:55 +0000 General 0 2 <p>(In reply to Jozef Slezák from comment #0)<br/> &gt; Stop instantiating new thread for echo after switch connected. Rather<br/> &gt; prepare threadpool while starting OFP and reuse threads.<br/> &gt; <br/> &gt; @Override<br/> &gt; public void onSwitchIdleEvent(final SwitchIdleEvent notification) {<br/> &gt; new Thread(new Runnable() {</p> <p>So, when instantiating this new thread pool, what should be it's behaviour? Should it have fixed size or not limit and to just reuse previous threads when available? Also, should it automatically shutdown threads after timeout (ex. 60 seconds)?</p> <p>Right now, I came up with fixed thread pool with limit of # of available processors + 1, without any automatic shutdown after timeout.</p> <p>GERRIT: <a href="https://git.opendaylight.org/gerrit/#/c/39306" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/39306</a></p> Development External issue ID 5924 External issue URL Issue Type ODL SR Target Milestone Rank 0|i032qf: