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-675 OpenFlowPlugin <p>Using Beryllium-SR1, after installing the OpenFlow plugin using:<br/> feature:install odl-openflowplugin-flow-services-rest</p> <p>When the first switch connects, I see the following exception:<br/> opendaylight-user@root&gt;Exception in thread "Thread-59" java.net.BindException: Address already in use<br/> at sun.nio.ch.Net.bind0(Native Method)<br/> at sun.nio.ch.Net.bind(Net.java:463)<br/> at sun.nio.ch.Net.bind(Net.java:455)<br/> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)<br/> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)<br/> at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)<br/> at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)<br/> at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1089)<br/> at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:440)<br/> at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:425)<br/> at io.netty.channel.ChannelDuplexHandler.bind(ChannelDuplexHandler.java:38)<br/> at io.netty.handler.logging.LoggingHandler.bind(LoggingHandler.java:197)<br/> at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:440)<br/> at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:425)<br/> at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:903)<br/> at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)<br/> at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)<br/> at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)<br/> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)<br/> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)<br/> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)<br/> at java.lang.Thread.run(Thread.java:745)</p> <p>and I don't see any of the OpenFlow switches actually connect.</p> <p>Oddly, if you then shut down the controller (via Control-D) and relaunch it the exception doesn't occur and things seem to work right.</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-675

bind exception on first running openflow plugin

Bug Resolved Cannot Reproduce Unassigned Colin Dixon Sun, 24 Apr 2016 17:55:50 +0000 Mon, 27 Sep 2021 09:01:47 +0000 Thu, 28 Apr 2016 15:41:17 +0000 General 0 1 <p>This is when using Mininet 2.1.0.</p> <p>Colin, I just tried this and could not reproduce in my end. Normally this kind of failures are detected by the test automation, this is why I run to verify myself.</p> <p>I can reproduce this every time in an Vagrant box with the following versions:</p> <p>vagrant@vagrant-ubuntu-trusty-64:~$ uname -a<br/> Linux vagrant-ubuntu-trusty-64 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux<br/> vagrant@vagrant-ubuntu-trusty-64:~$ java -version<br/> java version "1.7.0_95"<br/> OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)<br/> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)</p> <p>I guess I should check the original Beryllium release and maybe try it with java 8.</p> <p>This is in a VM with only 2GB of RAM as well, which presumably should still work, but might not be something we're testing. I'll keep trying to pin down exactly why/where this is happening.</p> <p>It's also frustrating to debug as it's not clear where we're spinning up this thread from the Exception.</p> <p>Bumping memory to 4GB did nothing.</p> <p>More investigation shows that I really don't need to launch mininet at all. The error just comes up if I install odl-openflowplugin-flow-services and wait about 30 seconds.</p> <p>It turns out that installing mininet automatically ran a copy of NOX that was listening on port 6633.</p> Development External issue ID 5789 External issue URL Rank 0|i032m7: