cas protocol behind an F5

[Paul B. Henson]

> From: Niva Agmon
> Sent: Wednesday, September 14, 2016 9:24 AM
>
> I updated our config based on your example with used heap percentage and
> that seemed to do the trick (was still getting the exception after changing the
> default hazelcast.max.no.heartbeat.seconds to 300).

To clarify, you don't need to explicitly set at 300, if you leave it out completely that is the default.

But you say you stopped getting the error on shutdown after you added the max-size-policy and eviction-policy configuration? That's interesting. Perhaps you were using most of your allocated heap memory and for some reason that was causing problems during shutdown? Ideally you don't want to run into the Hazelcast map size caps, as it basically means you are discarding sessions before your idp configuration so dictates (but which is still preferable to running out of memory and blowing up). How much memory do you have allocated to the heap on the system? Would it be possible to allocate any additional?

--
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768