Radoslav Husar created WFLY-9381: ------------------------------------ Summary: Reloading fails with BindException when TUNNEL protocol is configured with socket-binding Key: WFLY-9381 URL: https://issues.jboss.org/browse/WFLY-9381 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.CR1 Reporter: Radoslav Husar Assignee: Radoslav Husar {noformat} 15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed) at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104) at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.net.BindException: Address already in use (Bind failed) at java.net.PlainDatagramSocketImpl.bind0(Native Method) at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93) at java.net.DatagramSocket.bind(DatagramSocket.java:392) at java.net.DatagramSocket.<init>(DatagramSocket.java:242) at java.net.DatagramSocket.<init>(DatagramSocket.java:299) at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62) at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861) at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108) at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102) ... 5 more {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)