I'm getting an error "This page is taking longer to load than usual"while creating confluence page.
Asked by Ramesh Amadoru:

\* I'm getting an error "This page is taking longer to load than usual" while creating a confluence page.

\* Currently the Synchrony service of the environment is also running healthy.

\* I'm attaching the screenshots as well here.

\* Can anyone get any chance of resolving this problem?  

![Capture 2022-11-28 at 23.46.42.png](/t5/image/serverpage/image-id/227983iF5EEE6AD15A6DF13/image-size/large?v=v2&px=999 "Capture 2022-11-28 at 23.46.42.png")![Capture 2022-11-28 at 23.47.07.png](/t5/image/serverpage/image-id/227984iB7AE4AC1F01A29DF/image-size/large?v=v2&px=999 "Capture 2022-11-28 at 23.47.07.png")


Answers:
author: Fabio Racobaldo _Herzum_
body: Hi [@Ramesh Amadoru](/t5/user/viewprofilepage/user-id/1029258) ,

in my experience that happens when there is something wrong at collaborative editing side.

If you try to disable the collaborative editing, it should work (please, try). If so, please provide us atlassian-confluence.log entries that appear when the problem appear.

Hope this helps,

Fabio

comments: author: Ramesh Amadoru
body: Hi [@Fabio Racobaldo _Herzum_](/t5/user/viewprofilepage/user-id/781528) ,

\* Thanks for your suggestion. This started happening after promoting the server to the data center with a single node.

\* After that my Synchrony service didn't start and after debugging and trading the Confluence.log, found there is an ownership issue related to one jar file related to the Synchrony service in the Confluence-Installation directory.

\* So I've assigned the proper ownerships to installation and home directories and restarted the confluence which started the Synchrony service correctly. I even now restart or stop and restart the Synchrony service without any issue.

\* But when I try to create a page it gives me this error even though the Synchrony service fully running.   
\* The Synchrony logs don't show any errors or warnings, but I can see some warnings related to the "hazelcast.util.executor".  
\* I've attached the Confluence-home logs related to the error as well.  

2022-11-29 19:02:11,141 WARN \[hz.confluence.cached.thread-10\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:02:54,209 INFO \[Caesium-1-1\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:04:11,141 WARN \[hz.confluence.cached.thread-6\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:06:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:07:54,208 INFO \[Caesium-1-1\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:08:11,141 WARN \[hz.confluence.cached.thread-5\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:10:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:12:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:12:54,208 INFO \[Caesium-1-4\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:14:11,141 WARN \[hz.confluence.cached.thread-10\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServi...  
Collapse


author: Brant Schroeder
body: [@Ramesh Amadoru](/t5/user/viewprofilepage/user-id/1029258) did you recently restart the service? It could be a number of things, like not enough ram, an app not loading, etc. You should check your server logs and see what errors are being produced. Sometime a simple restart will fix the issue other times you might have to make some adjustments. [https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html#:\~:text=If%20you%20request%20help%20from,to%20create%20a%20Support%20Zip.](https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html#:~:text=If%20you%20request%20help%20from,to%20create%20a%20Support%20Zip.)

comments: author: Ramesh Amadoru
body: Hi [@Brant Schroeder](/t5/user/viewprofilepage/user-id/769100) I've restarted the Synchrony service which started successfully. But the issue still persists. I was able to start the Synchrony service which was not running before after closely monitoring the COnfluence-Home logs. But I cannot see anything other than the warning related to the "hazelcast.util.executor".  

This is what the home logs shows related to the error.  

2022-11-29 19:02:11,141 WARN \[hz.confluence.cached.thread-10\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:02:54,209 INFO \[Caesium-1-1\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:04:11,141 WARN \[hz.confluence.cached.thread-6\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:06:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:07:54,208 INFO \[Caesium-1-1\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:08:11,141 WARN \[hz.confluence.cached.thread-5\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:10:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:12:11,141 WARN \[hz.confluence.cached.thread-1\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:227)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)  
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64)  
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80)  
2022-11-29 19:12:54,208 INFO \[Caesium-1-4\] \[service.stepexecutor.export.SpaceExportCacheService\] removeExpiredCacheEntries Removing export cache entries that have exceeded their TTL.  
2022-11-29 19:14:11,141 WARN \[hz.confluence.cached.thread-10\] \[internal.cluster.impl.MulticastService\] log \[10.10.0.21\]:5801 \[Confluence-qa2\] \[3.12.11\] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time.  
java.io.IOException: Message too long  
at java.base/java.net.PlainDatagramSocketImpl.send0(Native Method)  
at java.base/java.net.AbstractPlainDatagramSocketImpl.send(Unknown Source)  
at java.base/java.net.DatagramSocket.send(Unknown Source)  
at com.hazelcast.internal.cluster.impl.MulticastService.send(MulticastService.java:284)  
at com.hazelcast.internal.cluster.impl.MulticastJoiner.searchForOtherClusters(MulticastJoiner.java:113)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.searchForOtherClusters(SplitBrainHandler.java:75)  
at com.hazelcast.internal.cluster.impl.SplitBrainHandler.run(SplitBrainHandler.java:42)  
at com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcurrentExecutionDecorator$DelegateDecorator.run(DelegateAndSkipOnConcurrentExecutionDecorator.java:77)  
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServi...  
Collapse  


author: Brant Schroeder
body: [@Ramesh Amadoru](/t5/user/viewprofilepage/user-id/1029258) take a look at this <https://confluence.atlassian.com/conf716/data-center-troubleshooting-1108683487.html> specifically the items around multicast.


author: Rilwan Ahmed
body: Hi [@Ramesh Amadoru](/t5/user/viewprofilepage/user-id/1029258) ,

1. Are you facing this issue only on creating the new page OR even when you edit and save the page ?
2. Is it for only one page ?
3. Do you have any add-ons/extenstions in your browser ? Disable them and retry OR try in another browser.  
   Try to log out, login back and check again. Also clear all your browser cache.
4. Is the issue only for you OR for all users ?
5. Did you check the Atlassian-confluence.log or Synchrony log ?

comments: author: Ramesh Amadoru
body: Hi [@Rilwan Ahmed](/t5/user/viewprofilepage/user-id/716861)

Regarding your first and second questions: I'm facing this issue while creating and editing both and it happens across the environment.

As you suggest, I tried with Edge and Chrome browsers as well as in incognito mode, but, there is no behavior change.   

I was able to start the Synchrony service which was not running before after closely monitoring the Confluence-Home logs. But I cannot see anything other than the warning related to the "hazelcast.util.executor".


Tags: confluence-server

data-center

server