On 06/11/2016 05:44 AM, PUZZLE wrote: > Here is a new error while launching the "dropallpacketsrpc on" command in ODL: > > *opendaylight-user@root>dropallpacketsrpc on* > *Exception in thread "Thread-56" java.net.BindException: Address already in > use*
My bet is that you have something else already running that's using a port that you are trying to use here. Like, for example, if you forgot that you have ODL w/ openflowplugin installed running on the same system, and then you tried to start another one. This would be the exact error you'd see in that case. JamO > * at sun.nio.ch.Net.bind0(Native Method)* > * at sun.nio.ch.Net.bind(Net.java:437)* > * at sun.nio.ch.Net.bind(Net.java:429)* > * at > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)* > * at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)* > * at > io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)* > * at > io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)* > * at > io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1081)* > * at > io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502)* > * at > io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)* > * at > io.netty.channel.ChannelDuplexHandler.bind(ChannelDuplexHandler.java:38)* > * at > io.netty.handler.logging.LoggingHandler.bind(LoggingHandler.java:240)* > * at > io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502)* > * at > io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)* > * at > io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904)* > * at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)* > * at > io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)* > * at > io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)* > * at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)* > * at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)* > * at > io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)* > * at java.lang.Thread.run(Thread.java:745)* > *Exception in thread "Thread-57" java.net.BindException: Address already in > use* > * at sun.nio.ch.Net.bind0(Native Method)* > * at sun.nio.ch.Net.bind(Net.java:437)* > * at sun.nio.ch.Net.bind(Net.java:429)* > * at > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)* > * at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)* > * at > io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)* > * at > io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)* > * at > io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1081)* > * at > io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502)* > * at > io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)* > * at > io.netty.channel.ChannelDuplexHandler.bind(ChannelDuplexHandler.java:38)* > * at > io.netty.handler.logging.LoggingHandler.bind(LoggingHandler.java:240)* > * at > io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502)* > * at > io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487)* > * at > io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904)* > * at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)* > * at > io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)* > * at > io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357)* > * at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)* > * at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)* > * at > io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)* > * at java.lang.Thread.run(Thread.java:745)* > *Error executing command: DropTest startup fail! Try again later.* > > > I don't get why ODL keeps giving me these errors, i think the use of Java > complicate things too much! i worked with RYU > (written in python) and it was the friendliest controller compared to ODL, > ONOS and Floodlight ! > > 2016-06-10 20:20 GMT+00:00 PUZZLE <[email protected] > <mailto:[email protected]>>: > > This message appears especially when choosing a big number of switches > (256 switches) > and even started to show when i used just a 64switches but with a big > number of hosts (100000hosts) > > > > 2016-06-10 16:52 GMT+00:00 Jamo Luhrsen <[email protected] > <mailto:[email protected]>>: > > my guess is that it's some trouble with how cbench is > starting/stopping it's > simulated switch connections. Assuming that from the > "HandshakeStepWrapper" > and the rejected strings. Probably ODL didn't like how cbench was > connecting > in some case. > > maybe you see it every time you run the test? > > JamO > > On 06/10/2016 08:17 AM, PUZZLE wrote: > > another one : > > > > *Exception in thread "Thread-232" > java.util.concurrent.RejectedExecutionException: Task > > > org.opendaylight.openflowplugin.openflow.md.core.HandshakeStepWrapper@53081ded > rejected from > > > org.opendaylight.openflowplugin.openflow.md.core.ThreadPoolLoggingExecutor@5dcff9fc[Terminated, > pool size = 0, active threads > > = 0, queued tasks = 0, completed tasks = 1]* > > * at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)* > > * at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)* > > * at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)* > > * at > > > > org.opendaylight.openflowplugin.openflow.md.core.ConnectionConductorImpl.onConnectionReady(ConnectionConductorImpl.java:451)* > > * at > > > > org.opendaylight.openflowjava.protocol.impl.core.connection.ConnectionAdapterImpl$1.run(ConnectionAdapterImpl.java:185)* > > * at java.lang.Thread.run(Thread.java:745)* > > > > > > > > > > 2016-06-10 14:03 GMT+00:00 PUZZLE <[email protected] > <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>>: > > > > Hi, > > when i was running cbench against ODL iwas gestting this > message: (especially with a high number of hosts) > > > > *Exception in thread "Thread-108" > java.util.concurrent.RejectedExecutionException: Task > > > org.opendaylight.openflowplugin.openflow.md.core.HandshakeStepWrapper@572e29bd > rejected from > > > org.opendaylight.openflowplugin.openflow.md.core.ThreadPoolLoggingExecutor@59e9dd28[Terminated, > pool size = 0, active > > threads = 0, queued tasks = 0, completed tasks = 1]* > > * at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)* > > * at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)* > > * at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)* > > * at > > > > org.opendaylight.openflowplugin.openflow.md.core.ConnectionConductorImpl.onConnectionReady(ConnectionConductorImpl.java:451)* > > * at > > > > org.opendaylight.openflowjava.protocol.impl.core.connection.ConnectionAdapterImpl$1.run(ConnectionAdapterImpl.java:185)* > > * at java.lang.Thread.run(Thread.java:745)* > > > > > > What does this mean? is it possible that results may change > based on tis? > > Thank you, > > Best > > > > > > > > > > _______________________________________________ > > openflowplugin-dev mailing list > > [email protected] > <mailto:[email protected]> > > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > > > > > _______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
