My Oracle Support Banner

Unable to Change The Overflow Cache Name or Overflow Cache Threshold With Java System Properties (Doc ID 1342994.1)

Last updated on APRIL 29, 2020

Applies to:

Oracle Coherence - Version 3.6.1 and later
Information in this document applies to any platform.

Symptoms

Coherence*Web has a set of Context parameters that can used to control its configuration. These can either be set in a web application's web.xml file, or can (in theory), be set as system properties.

In this problem the issue is that two of the parameters relating to the overflow attributes that used in the split session model (the default), are not set by their appropriate system properties:

For example, if you were to set the system properties for those attributes to the following values:

-Dcoherence.attribute.overflow.threshold=20480
-Dcoherence.session.overflow.cachename=my_custom_cache


and the property for the cache name, which can be overridden correctly:

-Dcoherence.session.cachename=my-session-storage


When you use a tool like jconsole to examine the Coherence*Web HttpSessionManager MBean, you'd see that neither the overflow threshold or overflow cache name is using the new values, as shown in this image:



While the SessionCacheName is correct, the OverflowCacheName and OverflowThreshold are still set to their default values.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.