There is a regression against EAP 7.0.0.ER5. If server is reloaded multiple times then sometimes following exception is logged in server.log (attached):
11:56:35,172 WARN [org.apache.activemq.artemis.core.client] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@2b4ecad5-1022697750)) null: java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1039) [rt.jar:1.8.0_71] at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) [rt.jar:1.8.0_71] at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) [rt.jar:1.8.0_71] at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.waitForTopology(ClientSessionFactoryImpl.java:453) [artemis-core-client-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:790) [artemis-core-client-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:614) [artemis-core-client-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:595) [artemis-core-client-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at org.apache.activemq.artemis.core.server.cluster.ClusterController$ConnectRunnable.run(ClusterController.java:405) [artemis-server-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100) [artemis-core-client-1.1.0.SP13-redhat-1.jar:1.1.0.SP13-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
Fast sequence of :reload calls causes that Artemis is stopped before Artemis managed to update its own cluster topology. (Note there is just one server and no other)
Customer impact:
There is no data inconsistency. Issue is logged warning during fast reloading.
Test scenario:
1. Start EAP 7.0.0.ER6 in standalone-full-ha.xml profile
2. Call :reload multiple times in a quick succession
Expected behavior:
No interrupted exception will be logged.
- is cloned by
-
JBEAP-5831 (7.1.0) Calling reload operation causes: "java.lang.InterruptedException"
- Closed
- is related to
-
JBEAP-3635 Multiple :reload of server causes "java.lang.OutOfMemoryError: GC overhead limit exceeded"
- Closed