How To Disable Use Of Local-Cache For session IDs and Its Data In The Coherence*Web WebLogic Server?
(Doc ID 2221420.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Coherence - Version 184.108.40.206 and later
Information in this document applies to any platform.
Customer is using Coherence*Web with 220.127.116.11 and session data is not carrying total serializable attributes so coherence*Web sessions' data is getting stored in the local-cache. The JVMs heap is growing and GC collections are frequent and its GC pauses are contributing to high communication delays in the cluster. On analysis it got identified that a known issue, <Bug 17483865>, fixed in the patch 11 leaving local attributes not GCed even after session invalidation. However customer did not upgrade to latest patch 16 for 3.7.1 and made all the session data serializable even then there is some amount of local-cache is in use. That is because the session data local-cache is holding the session IDs.
This document helps on to disable use of local-cache for session IDs and its data in the coherence*web WebLogic Server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document