Denis, Thanks. Meanwhile, we made some progress...the via workaround seems to use these two flags in the thick client config -DIGNITE_SKIP_PARTITION_SIZE_VALIDATION -DIGNITE_EXCHANGE_HISTORY_SIZE=8 So far, we haven't seen clients going OOM for about 24 hours (still watching) Based on the logs, you could see there is a partition map exchanged among the clients and feels like messages continuously get stored on the clients causing this problem.
- Re: Ignite 2.7.0: Ignite client:: memory leak Mahesh Renduchintala
- Re: Ignite 2.7.0: Ignite client:: memory leak Denis Magda
- Re: Ignite 2.7.0: Ignite client:: memory lea... Mahesh Renduchintala
- Re: Ignite 2.7.0: Ignite client:: memory... Denis Magda
- Re: Ignite 2.7.0: Ignite client:: me... Mahesh Renduchintala
- Re: Ignite 2.7.0: Ignite client... Andrei Aleksandrov
- Re: Ignite 2.7.0: Ignite cl... Denis Magda
- Re: Ignite 2.7.0: Ignit... Ilya Kasnacheev
- Re: Ignite 2.7.0: Ignit... Denis Magda
- Re: Ignite 2.7.0: Ignit... Mahesh Renduchintala
- Re: Ignite 2.7.0: Ignit... Mahesh Renduchintala