Sathish,
Your async-backup-count and backup-count have non default values. Is it
possible these values are causing hazelcast to consume memory?
Try using default values to see if memory use improves.
You can monitor the JVM with JDK Misson Control or jConsole.
Ray
P.S. To keep your config
Hi Sathish
Did you check the port(5701) access and connectivity of hazelcast members?
you can set the hazelcast.log.level to debug for more details in log.
On Tuesday, November 14, 2023 at 10:36:28 PM UTC+3:30 Sathish Sekar wrote:
> Hi Team,
>
> Hazelcast is causing problem. Since we have 3
Hi Team,
Hazelcast is causing problem. Since we have 3 servers clustered. Earlier we
have tomcat memory of 512mb min and max. I posted in CAS community and they
suggested to increase memory by max 2gb. It is running fine for 12 days and
stopped showing heap memory issue. The following are
Hi Team,
Prod server stopped due to following issues. Kindly help. I'm facing heap
memory issue for long time :(
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread
"hz.10.34.196.43.MetricsRegistry.thread-2"
Exception: java.lang.OutOfMemoryError thrown
Not sure why it's complaining about an IP address that's not in your
configuration. I wonder if it's picking up a second IP that's configured?
You could try setting this:
cas.ticket.registry.hazelcast.cluster.core.instance-name=localhost
Hi Team,
I'm upgrading CAS 6.3.7.4 to 6.6.9. The below properties I have added
for Hazelcast and Ticket Registry in upgraded version. I'm seeing this
error which is printed in logs often. Kindly check below properties and
guide me if any modification/addition/deletion of properties.
ERROR
