[jboss-jira] [JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown

[David Lloyd (JIRA)]

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

David Lloyd commented on WFLY-5994:
-----------------------------------

Here's how we fix this:
# Introduce a new XNIO worker service (ON_DEMAND is the best choice here) which is targeted for management only (separate from I/O subsystem), using the configuration that is presently defined in {{org.jboss.as.domain.http.server.ManagementHttpServer}} (NOTE: where should this service live?)
# Modify {{org.jboss.as.domain.http.server.ManagementHttpServer}} so that it sets a (final) XnioWorker from a dependency which is injected from this shared service
# Modify {{org.jboss.as.domain.http.server.ManagementHttpServer#create}} to populate the new value from a parameter
# Modify {{org.jboss.as.server.mgmt.UndertowHttpManagementService}} to accept and use an XnioWorker dependency
# Modify {{org.jboss.as.host.controller.operations.HttpManagementAddHandler#installHttpManagementServices}} and {{org.jboss.as.server.operations.HttpManagementAddHandler#installHttpManagementConnector}} to supply the required service
# Modify {{org.jboss.as.remoting.RemotingServices}} to set a dependency on the new worker service in {{installRemotingManagementEndpoint}}
# Also modify {{installRemotingManagementEndpoint}} to use a plain {{EndpointService}} instead of the {{ManagementEndpointService}}
# Delete {{ManagementEndpointService}}

> RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
> --------------------------------------------------------------
>
>                 Key: WFLY-5994
>                 URL: https://issues.jboss.org/browse/WFLY-5994
>             Project: WildFly
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 10.0.0.CR5
>            Reporter: Rostislav Svoboda
>            Assignee: David Lloyd
>            Priority: Blocker
>
> WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop. 
> *reproduce*
> \# start WFLY 10 CR5
> {noformat}
> $ ./standalone.sh
> ...
> 10:30:46,536 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
> {noformat}
> \# shutdown via CLI
> {noformat}
> $ ./jboss-cli.sh -c shutdown
> {noformat}
> \# check console where WFLY 10 CR5 was started
> {noformat}
> 10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> 	at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> 	at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> 	at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> 	at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> 	at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> 	at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
> 	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)
> {noformat}
> {noformat}
> 10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> 	at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> 	at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
> 	at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
> 	at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
> 	at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
> 	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)
> {noformat}



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