Valerii Pekarskyi

Thanks for the answer! I am using JGroups 4.0.15.Final, and attached cluster configs to the first post in the thread. Did no customization in "client" cluster, and "server" cluster has UDP thread pool 0-20 comparing to the default 0-100. As problems now appears in "client" cluster instances it seems that the problem is caused by default 0-100 thread pool.

Hi there! Last several days I struggle with sporadic failures of instances running inside the JGroups cluster. I believe there is some cluster misconfiguration, and I try to find correct configuration, but with no much luck yet. May I ask for some advice? There are two types of failures I see in logs. There is a positive side that failed JVM generates heap dump that allows better diagnosis, so there could be something helpful there. A bit of background: JGroups is used in the client-server application...

Hi there! Last several days I struggle with sporadic failures of instances running inside the JGroups cluster. I believe there is some cluster misconfiguration, and I try to find correct configuration, but with no much luck yet. May I ask for some advice? There are two types of failures I see in logs. There is a positive side that failed JVM generates heap dump that allows better diagnosis, so there could be something helpful there. A bit of background: JGroups is used in the client-server application...

Hi there! Last several days I struggle with sporadic failures of instances running inside the JGroups cluster. I believe there is some cluster misconfiguration, and I try to find correct configuration, but with no much luck yet. May I ask for some advice? There are two types of failures I see in logs. There is a positive side that failed JVM generates heap dump that allows better diagnosis, so there could be something helpful there. A bit of background: JGroups is used in the client-server application...

Check for deadlocks in static init of parent/child classes