It was reported that MaxDailyCounterQueue is responsible for throwing java.util.ConcurrentModificationException, see the stack trace:
[2020-07-14 14:58:53:722] [WARNING ] [ResultsListener-socketReadThread-0 ] SocketThread$ResultsListener.run(): Protocol execution exception.
java.util.ConcurrentModificationException
at java.base/java.util.ArrayDeque.nonNullElementAt(ArrayDeque.java:271)
at java.base/java.util.ArrayDeque$DeqIterator.next(ArrayDeque.java:701)
at java.base/java.util.AbstractCollection.toString(AbstractCollection.java:472)
at tigase.stats.MaxDailyCounterQueue.add(MaxDailyCounterQueue.java:52)
at tigase.cluster.ClusterConnectionManager.nodeConnected(ClusterConnectionManager.java:328)
at tigase.cluster.ClusterController.nodeConnected(ClusterController.java:126)
at tigase.cluster.ClusterConnectionManager.serviceConnected(ClusterConnectionManager.java:777)
at tigase.cluster.ClusterConnectionManager.processHandshake(ClusterConnectionManager.java:908)
at tigase.cluster.ClusterConnectionManager.processSocketData(ClusterConnectionManager.java:424)
at tigase.server.ConnectionManager.packetsReady(ConnectionManager.java:347)
at tigase.server.ConnectionManager.packetsReady(ConnectionManager.java:61)
at tigase.net.IOService.call(IOService.java:202)
at tigase.xmpp.XMPPIOService.call(XMPPIOService.java:146)
at tigase.xmpp.XMPPIOService.call(XMPPIOService.java:51)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
wojciech.kapcia@tigase.net commented 4 years ago
Issue is fixed - I changed extended method as a quick workaround.
It was reported that
MaxDailyCounterQueue
is responsible for throwingjava.util.ConcurrentModificationException
, see the stack trace: