| commit | 369c64380201c450881ffb666c40526c48cb4d5d | [log] [tgz] |
|---|---|---|
| author | Pavlin Radoslavov <pavlin@onlab.us> | Wed Dec 03 16:25:14 2014 -0800 |
| committer | Gerrit Code Review <gerrit@onlab.us> | Thu Dec 04 02:06:53 2014 +0000 |
| tree | 2dee7f73a3fc25dd8affa35f59c8f767eb5dda71 | |
| parent | e1588ed28a7f37651971838cad590814f7e761b6 [diff] [blame] |
Use two thread pools for handling the OpenFlow STATS and BARRIER messages. This fixes a problem where a large number of incoming STATS messages is practically using all available threds from the pool (16), and there are no available threads to handle the BARRIER messages. Change-Id: I1130eb8f3b5a17d5d3a7825f32da68eacb99569a fixing other threadpool issues, ie. not using cachedThreadPool Change-Id: I40ef10e1f704aef779b2a23c0497dfb7992520eb
diff --git a/core/net/src/main/java/org/onosproject/net/flow/impl/FlowRuleManager.java b/core/net/src/main/java/org/onosproject/net/flow/impl/FlowRuleManager.java index 9578944..0f543d0 100644 --- a/core/net/src/main/java/org/onosproject/net/flow/impl/FlowRuleManager.java +++ b/core/net/src/main/java/org/onosproject/net/flow/impl/FlowRuleManager.java
@@ -103,7 +103,8 @@ @Activate public void activate() { - futureService = Executors.newCachedThreadPool(namedThreads("provider-future-listeners-%d")); + futureService = + Executors.newFixedThreadPool(32, namedThreads("provider-future-listeners-%d")); store.setDelegate(delegate); eventDispatcher.addSink(FlowRuleEvent.class, listenerRegistry); log.info("Started");