Hi Ray,
Your help really means a lot to me.
Adding more info: As of now, we have these hazelcast properties in production.
Please take a look & let me know if any of these configuration leads to memory leak.
cas.ticket.registry.hazelcast.page-size=500
cas.ticket.registry.hazelcast.cluster.members=10.xx...,10.xx..,10.xx..
cas.ticket.registry.hazelcast.cluster.instance-name=10.xx..
cas.ticket.registry.hazelcast.cluster.port=5701
cas.ticket.registry.hazelcast.enable-compression=false
cas.ticket.registry.hazelcast.enable-management-center-scripting=true
cas.ticket.registry.hazelcast.crypto.enabled=true
cas.ticket.registry.hazelcast.cluster.asyncBackupCount=1
cas.ticket.registry.hazelcast.cluster.backupCount=0
cas.ticket.registry.hazelcast.crypto.signing.key=keyyyyyyyyyyyyyyyyyyyyyyy
cas.ticket.registry.hazelcast.crypto.signing.keySize=512
cas.ticket.registry.hazelcast.crypto.encryption.key=keyyyyyyyyyyyyyyyyyyyyyyy
cas.ticket.registry.hazelcast.crypto.encryption.keySize=16
cas.ticket.registry.hazelcast.crypto.alg=AES
cas.ticket.registry.cleaner.schedule.start-delay=PT20S
cas.ticket.registry.cleaner.schedule.repeat-interval=PT3600000S
cas.ticket.registry.cleaner.schedule.enabled=true
Regards,
Morning.