[jboss-jira] [JBoss JIRA] (WFLY-5589) IllegalStateException when shutting down the server started with default standalone-full-ha.xml

Chao Wang (JIRA) issues at jboss.org
Wed Oct 28 03:55:00 EDT 2015


    [ https://issues.jboss.org/browse/WFLY-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122746#comment-13122746 ] 

Chao Wang commented on WFLY-5589:
---------------------------------

I think this may also happen to other potential unnamed datagram socket unregistration. IllegalStateException pops out due to https://github.com/wildfly/wildfly/commit/36f5bd99c8893a75ae0338708a5bd41263676060 as it uses UnnamedRegistryImpl.java which depends on address value of ManagedBinding.getBindAddress() to unregister.
However, before unregistering a managed binding, it first closes datagram socket. Thus, while UnnamedRegistryImpl unregisters binding and calls its superclass DatagramSocket.getLocalSocketAddress(), it gets null value because socket was already closed.

> 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: Jason Greene
>            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



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jboss-jira mailing list