Oracle Coherence 3.7 session reap cycle configuration in WebLogic Server (Doc ID 1350488.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Coherence - Version 3.7.0 and later
Information in this document applies to any platform.
***Checked for relevance on 19-MAR-2013***

Goal

In Coherence*Web, the HTTP session reap cycle is configured with the setting "coherence-reaperdaemon-cycle-seconds" in web.xml:

<context-param>
<param-name>coherence-reaperdaemon-cycle-seconds</param-name>
<param-value>600</param-value>
</context-param>


However, this setting is ignored when using Coherence*Web 3.7 and WebLogic (via the WebLogic SPI integration):

<Jun 15, 2011 10:03:07 AM PDT> <Notice> <StdErr> <BEA-000000> <2011-06-15 10:03:07.384/976.357 Oracle Coherence GE 3.7.0.1 <D5> (thread=SessionReaperDaemon[apps/webcasts, 2011-06-15 09:52:00.829], member=13): Next reap cycle will start in 59980ms.>

Solution

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