]
Chao Wang reassigned WFLY-5589:
-------------------------------
Assignee: Chao Wang (was: Jason Greene)
IllegalStateException when shutting down the server started with
default standalone-full-ha.xml
-----------------------------------------------------------------------------------------------
Key: WFLY-5589
URL:
https://issues.jboss.org/browse/WFLY-5589
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 10.0.0.CR4
Reporter: Martin Švehla
Assignee: Chao Wang
Priority: Critical
When I start WildFly 10.0.0.CR4 with default standalone-full-ha.xml configuration and
then shut it down, I'll get following ERROR in the server log:
{code}
09:18:19,143 ERROR [org.jgroups.JChannel] (MSC service thread 1-2) JGRP000020: failed
destroying the protocol stack: java.lang.IllegalStateException
at
org.jboss.as.network.SocketBindingManagerImpl$UnnamedRegistryImpl.unregisterBinding(SocketBindingManagerImpl.java:501)
at
org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73)
at
org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:148)
at org.jgroups.protocols.UDP.closeUnicastSocket(UDP.java:577)
at org.jgroups.protocols.UDP.destroySockets(UDP.java:429)
at org.jgroups.protocols.UDP.destroy(UDP.java:294)
at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:887)
at org.jgroups.JChannel.stopStack(JChannel.java:1005)
at org.jgroups.JChannel._close(JChannel.java:990)
at org.jgroups.JChannel.close(JChannel.java:385)
at
org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.stop(ChannelBuilder.java:91)
at
org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
at
org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
This is regression from CR3 build and might be related to fix for
https://issues.jboss.org/browse/WFCORE-1033