Description of problem: I am getting JBWEB003011: Error allocating socket processor on server stop. Version-Release number of selected component (if applicable): EAP 6.3.0.DR2 How reproducible: 5-10% chance Steps to Reproduce: I am using the domain with 4 servers and web console to reproduce it, but there may be a better reproducer than this. 1. Start the out-of-box domain and enter the web console. 2. Create server-one ... server four in main-server group to be able to manage all servers as server group. 3. Start/Restart/Stop the whole server group. Actual results: From time to time you get the following error message from one of the servers. [Server:server-three] 11:41:42,380 ERROR [org.apache.tomcat.util.net] (http-localhost/127.0.0.1:8330-Acceptor) JBWEB003011: Error allocating socket processor: java.util.concurrent.RejectedExecutionException: Task org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor@ccfef6f rejected from java.util.concurrent.ThreadPoolExecutor@277066fb[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] [Server:server-three] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) [rt.jar:1.7.0_40] [Server:server-three] at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) [rt.jar:1.7.0_40] [Server:server-three] at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) [rt.jar:1.7.0_40] [Server:server-three] at org.apache.tomcat.util.net.NioEndpoint.processChannel(NioEndpoint.java:453) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] [Server:server-three] at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:566) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] [Server:server-three] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] Expected results: Server will stop without any error messages.
I'm getting same message in standalone mode.
Increasing severity and requesting blocker flag as this is regression against EAP 6.2.0.GA and my test results are highly distorted by this error.
*** This bug has been marked as a duplicate of bug 1065932 ***