Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
7.3.0.GA.CR4, 7.4.10.CR1
-
None
Description
... 08:34:32,764 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 7) MODCLUSTER000002: Initiating mod_cluster shutdown 08:34:32,765 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 90) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 08:34:32,776 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 4) AMQ151003: resource adaptor stopped 08:34:32,777 ERROR [org.xnio.listener] (management Accept) XNIO001007: A channel event listener threw an exception: java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating at org.xnio.nio.WorkerThread.execute(WorkerThread.java:620) at org.xnio.nio.QueuedNioTcpServer2.handleReady(QueuedNioTcpServer2.java:160) at org.xnio.nio.QueuedNioTcpServer2.lambda$new$1(QueuedNioTcpServer2.java:58) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.nio.NioTcpServerHandle.handleReady(NioTcpServerHandle.java:65) at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) 08:34:32,861 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 4) AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.9.0.redhat-00005 [4456e98f-629f-11ea-9c2a-54e1addf5d3e] stopped, uptime 0.289 seconds ...
could be seen in server logs from time to time after the reload operation via org.jboss.as.cli.scriptsupport.CLI.
Reproduce
- start standalone server with standalon-full-ha.xml
- watch the server log (e.g. tail -f)
- execute the reproducer code with jboss-eap-7.3/bin/client/jboss-cli-client.jar on classpath
import org.jboss.as.cli.scriptsupport.CLI; public class Demo { public static void main(String[] args) { CLI cli = CLI.newInstance(); cli.connect(); for (int i = 0; i < 100; i++) { System.out.println("######## TEST: " + i); cli.cmd("reload"); // Thread.sleep(3000L); // this one doesn't help here } cli.disconnect(); } }
I do not see the exception if using CLI (jboss-cli.sh) or Management API. The exception appears in ~2 % of cases.
Attachments
Issue Links
- is cloned by
-
-
- New
-
