My Oracle Support Banner

How To Handle Store Failures Using Write-Behind Caching (Doc ID 978862.1)

Last updated on MAY 04, 2021

Applies to:

Oracle Coherence - Version 3.5.0 to 3.5.3 [Release AS10g]
Information in this document applies to any platform.
***Checked for relevance on 22-FEB-2013***

Goal

The following how to shows how to deal with store failures in a write behind scenario. The client performing the write to the cache will not have an exception thrown to it upon failure, so it is incapable of handling the exception. Here we setup a demo showing how a store failure will be requeued and continually re-tried until it has successfully been stored.

Note that the behaviour of the write behind queueing changes in Coherence 3.6 and later, where the <write-requeue-threshold> no longer sets a maximum size for re-queued, and simply determines how frequently information on the size of the queue is reported.

 

Solution

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
Goal
Solution
 How This Works
 Strategy
 Demo
 1. Pre Steps
 2. Database Setup
 3. Start Cache Server
 4. Start Client
 More Information
References

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