Re: Threads got stuck

Hi. After restarting servers, that issue did not occur again. I guess for some reason the cluster did not start normally. Thanks responding so quick. Regards. On Tue, Oct 25, 2016 at 11:31 AM, Yakov Zhdanov wrote: > Alper, thanks for clarification, this will definitely

Re: Threads got stuck

Alper, thanks for clarification, this will definitely help after we get the info I requested. This is the only way to go with the investigation. --Yakov 2016-10-25 11:20 GMT+03:00 Alper Tekinalp : > Hi Yakov. > > I should also mention that we load cache data from one server and

Re: Threads got stuck

Hi Yakov. I should also mention that we load cache data from one server and wait the data to be replicated to others. Can that cause such a situation, too? On Tue, Oct 25, 2016 at 11:14 AM, Yakov Zhdanov wrote: > Alper, > > There can be multiple reasons. > > Can you please

Re: Threads got stuck

Alper, There can be multiple reasons. Can you please reproduce the issue one more time, collect and share the following with us: 1. collect all the logs from all the nodes - clients and servers 2. take threaddumps of all JVMs (from all nodes) with jstack -l --Yakov 2016-10-25 10:49 GMT+03:00

Re: Threads got stuck

Hi. There is also a few logs as : Failed to register marshalled class for more than 10 times in a row (may affect performance). Can it be releated? On Tue, Oct 25, 2016 at 10:32 AM, Alper Tekinalp wrote: > Hi all. > > We have 3 servers and cache configuration like: > >

Threads got stuck

Hi all. We have 3 servers and cache configuration like: For our worker threads we check heartbeat and if a thread did not sent heart beat for