[jboss-jira] [JBoss JIRA] (WFCORE-227) RejectedExecutionException when closing ModelControllerClient client

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-227:
------------------------------------
    Fix Version/s:     (was: 1.0.0.Alpha13)
         Assignee: David Lloyd
      Component/s: Remoting


David, per chat discussion it looks like you are looking at this in terms of a remoting change. If there's anything we must do to mitigate this, let me know.

I find it a bit odd that RemotingModelControllerClient.close() is calling channelAssociation.shutdownNow *after* closing the channel and endpoint, and if were done first perhaps the result could be that ManagementChannelReceiver stops registering itself after each message. But there's probably still a race there anyway and I don't want to start mucking with this stuff unless I need to.

> RejectedExecutionException when closing ModelControllerClient client
> --------------------------------------------------------------------
>
>                 Key: WFCORE-227
>                 URL: https://issues.jboss.org/browse/WFCORE-227
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management, Remoting
>    Affects Versions: 1.0.0.Alpha11
>            Reporter: Alessio Soldano
>            Assignee: David Lloyd
>
> After wildfly-core 1.0.0.Alpha11 has been included in WFLY master, I'm seeing hundreds of the following exceptions in the logs when running the JBossWS-CXF testsuite:
> {noformat}
> Exception in thread "Remoting "management-client" task-4" java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteConnectionChannel$3 at 5651c0c2 rejected from org.xnio.XnioWorker$TaskPool at 11462cd4[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 4]
> 	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048)
> 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
> 	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372)
> 	at org.xnio.XnioWorker.execute(XnioWorker.java:741)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.receiveMessage(RemoteConnectionChannel.java:363)
> 	at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:107)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:451)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception is logged just after the org.jboss.as.webservices.deployer.RemoteDeployer calls the RemotingModelControllerClient#close method.
> The issue seems to be related to some kind of race condition, as trying to reproduce it with an attached debugger is not possible.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)