This discussion is archived
0 Replies Latest reply: Dec 16, 2013 10:46 PM by user621063 RSS

CacheStore 3.7 configuration does not work with Coherence 12c

user621063 Newbie
Currently Being Moderated

Hi,

 

The following CacheStore configuration works fine with Coherence 3.7.1.6 but it does not work with Coherence Oracle Coherence 12.1.2.0.1.

The implemented NoPersistenceCacheStore() constructor is invoked successfully in 12c during the startup, but there is no following calls to the store()/storeAll() at all.

Could you advise what has changed in Coherence 12c which leads to this problem?

Thanks for your help in advance.

 

        <cache-name>RatedEvent</cache-name>
        <scheme-name>default-distributed-expiry</scheme-name>
        <init-params>
            <init-param>
                <param-name>expiry-delay</param-name>
                <param-value>5m</param-value>
            </init-param>
            <init-param>
                <param-name>write-delay</param-name>
                <param-value>1s</param-value>
            </init-param>
            <init-param>
                <param-name>cache-store</param-name>
                <param-value>oracle.communication.brm.charging.util.coherence.internal.NoPersistenceCacheStore
                </param-value>
            </init-param>
            <init-param>
                <param-name>back-size-limit</param-name>
                <param-value>600MB</param-value>
            </init-param>
        </init-params>
    </cache-mapping>

 

 

 

    <read-write-backing-map-scheme>
        <scheme-name>rw-bm</scheme-name>
        <internal-cache-scheme>
            <local-scheme>
                <unit-calculator>BINARY</unit-calculator>
                <expiry-delay>{expiry-delay 0}</expiry-delay>
                <high-units>{back-size-limit 0}</high-units>
            </local-scheme>
        </internal-cache-scheme>
        <cachestore-scheme>
            <class-scheme>
                <class-name>{cache-store}</class-name>
            </class-scheme>
            <operation-bundling>
                <bundle-config>
                    <operation-name>all</operation-name>
                    <preferred-size>1000</preferred-size>
                    <auto-adjust>true</auto-adjust>
                </bundle-config>
            </operation-bundling>
        </cachestore-scheme>
        <write-delay>{write-delay 0}</write-delay>
        <write-batch-factor>0.75</write-batch-factor>
        <!-- Specifies the maximum size of the write-behind queue for which failed
             cache store write operations are re-queued. If the current queue size < threshold then the
             failed operations are requeued. Keeping it Integer.MAX_VALUE to make sure no updates are lost.
             Though, a failure could cause OutOfMemoryException but with NoSQL clustered this is a risk
             worth taking.
          -->
        <write-requeue-threshold>2147483647</write-requeue-threshold>
    </read-write-backing-map-scheme>

 

 

 

    <distributed-scheme>
        <scheme-name>default-distributed-expiry</scheme-name>
        <scheme-ref>default-distributed</scheme-ref>
        <backing-map-scheme>
            <read-write-backing-map-scheme>
                <scheme-ref>rw-bm</scheme-ref>
            </read-write-backing-map-scheme>
        </backing-map-scheme>
    </distributed-scheme>

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points