How To Use Coherence*Web Parallel Session Reaper Executing Under wm/CoherenceWorkManager (Doc ID 2218268.1)

Last updated on JANUARY 04, 2017

Applies to:

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

Goal

Each Coherence*Web instance has a Session Reaper that will periodically iterate through all of the sessions in the session cache and check for expired sessions. With context parameter, coherence-reaperdaemon-parallel, enabled Session Reaper will invalidate expired sessions in parallel.

Coherence*Web uses a work manager to retrieve threads to execute the parallel reaping. WebLogic Server defines a default work manager, wm/CoherenceWorkManager, which it will attempt to use. If no work manager is defined with that name, it will use the default work manager implemented in Coherence.

In the Coherence Version 12c and above though the work manager got defined in the admin console for the weblogic servers but coherence session reaper at runtime not using that threads from that work manager.

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