Read-through configuration problems

Question

Hi!
I have problem with read-through example. The DataLoader object is created (somewhere in Coherence) but method load(Object key) is never called. Please help.
public class DataLoader extends AbstractCacheLoader {
    private static HashMap<String, String> hashMap = new HashMap<String, String>();
    static {
        hashMap.put("A", "a");
        hashMap.put("B", "b");
        hashMap.put("C", "c");
        hashMap.put("D", "d");
        hashMap.put("E", "f");
        hashMap.put("F", "g");
    public DataLoader() {
        System.out.println("Instance of DataLoader");
    public Object load(Object key) {
        return hashMap.get(key);
}Config files:
<cache-config>
    <caching-scheme-mapping>
        <cache-mapping>
            <cache-name>ABC</cache-name>
            <scheme-name>SamplePartitionedDatabaseScheme</scheme-name>
        </cache-mapping>
    </caching-scheme-mapping>
    <caching-schemes>
        <distributed-scheme>
            <scheme-name>SamplePartitionedDatabaseScheme</scheme-name>
            <backing-map-scheme>
                <read-write-backing-map-scheme>
                    <scheme-ref>SampleDatabaseScheme</scheme-ref>
                </read-write-backing-map-scheme>
            </backing-map-scheme>
        </distributed-scheme>
        <read-write-backing-map-scheme>
            <scheme-name>SampleDatabaseScheme</scheme-name>
            <internal-cache-scheme>
                <local-scheme>
                    <scheme-ref>SampleMemoryScheme</scheme-ref>
                </local-scheme>
            </internal-cache-scheme>
            <cachestore-scheme>
                <class-scheme>
                    <class-name>com.example.DataLoader</class-name>
                </class-scheme>
            </cachestore-scheme>
        </read-write-backing-map-scheme>
        <local-scheme>
            <scheme-name>SampleMemoryScheme</scheme-name>
        </local-scheme>
    </caching-schemes>
</cache-config>and
<coherence>
    <cluster-config>
        <member-identity>
            <cluster-name>thecluster</cluster-name>
        </member-identity>
        <multicast-listener>
            <port>9100</port>
            <time-to-live>0</time-to-live>
        </multicast-listener>
    </cluster-config>
</coherence>Starting server
package com.example;
import com.tangosol.net.DefaultCacheServer;
import com.tangosol.net.DefaultConfigurableCacheFactory;
public class Server {
    public static void main(String[] args) {
        DefaultConfigurableCacheFactory factory;
        factory = new DefaultConfigurableCacheFactory();
        DefaultCacheServer dcs = new DefaultCacheServer(factory);
        dcs.startAndMonitor(5000);
}Getting data
package com.example;
import com.tangosol.net.CacheFactory;
import com.tangosol.net.NamedCache;
public class Reader {
    public static void main(String[] args) {
        CacheFactory.ensureCluster();
        NamedCache cache = CacheFactory.getCache("ABC");
        System.out.println("Value in cache is: " + cache.get("A"));
        System.out.println("Value in cache is: " + cache.get("B"));
        System.out.println("Value in cache is: " + cache.get("C"));
        System.out.println("Value in cache is: " + cache.get("D"));
}Result
Value in cache is: null
Value in cache is: null
Value in cache is: null
Value in cache is: null

Answer 1

Hi St,
Actually, looking at the code again, your server will not be using your custom configuration.
I'm not sure why you have written the code like that but there is no need to create a DefaultConfigurableCacheFactory instance; Coherence will take care of that. As you have used the default constructor for DefaultConfigurableCacheFactory it will be using a configuration file called coherence-cache-config.xml; is that what your file is called?
All your Server main method needs to do is this...
package com.example;
import com.tangosol.net.DefaultCacheServer;
public class Server {
    public static void main(String[] args) {
        DefaultCacheServer.main(args);
}Which is actually nothing more than running DefaultCacheServer, so you do not even need a custom Server class.
JK