Entries In the Coherence*Web Local Attribute Cache Are Not Reaped After The Session Expires

(Doc ID 1607367.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Coherence - Version to [Release AS10g]
Information in this document applies to any platform.


Customer is facing a memory leak in WebLogic Server instances, where they are sharing a subset of Session attributes among two different webapps using Coherence*Web. This memory leak eventually fills the entire heap of the WebLogic Server instances, leading them to an unrecoverable state which requires the instances to be shutdown and restarted.

Heap dumps on the failing WLS instances show how the main leak suspect points to a cache used by Coherence*Web to store locally the session attributes (local-attribute-storage). This cache is the one that increases its size until the crash of the WebLogic instance with an OutOfMemoryError


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms