Mahesh, Hmm, yes, I remember one use case when the OOM was addressed by tweaking IGNITE_EXCHANGE_HISTORY_SIZE. In that scenario, the environment had not much RAM and the team couldn't allocate enough RAM for Java Heap.
How about your scenario? Have you tried to give 2GB or more to the app? - Denis On Thu, Aug 1, 2019 at 8:16 PM Mahesh Renduchintala < [email protected]> wrote: > 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. > >
