[jboss-user] [JBoss Cache: Core Edition] - Jdbc Cahce Loader Issue

[shanthi_jbosscache]

Hi,

I am using JBoss cache(1.4.1SP8) in webapplication which is deployed in weblogic clustered environment. I have two management ports.I am using JDBC Cache Loader and cache is clustered across the weblogic portals.

I started the portal1 server succeessfully and cache also started. All the records are in the DB also.When I start the Portal2 server, I stop the server by killing the process before completion of startup.

Now the DB contains very less records. I think StoreEntireState method is called by Cacheloader and it replaces the records in the db with the data which was loaded in the cache during startup of portal2 server. is it true? plese help...

 My configuration details are below


        
            
                <!-- UDP: if you have a multihomed machine,
                set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
                -->
                <!-- UDP: On Windows machines, because of the media sense feature
                 being broken with multicast (even after disabling media sense)
                 set the loopback attribute to true -->
                <UDP mcast_addr="224.1.2.3" mcast_port="47700"
                    ip_ttl="64" ip_mcast="true"
                    mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
                    ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
                    loopback="false" bind_addr="192.168.100.8"/>
                <PING timeout="2000" num_initial_members="3"
                    up_thread="false" down_thread="false"/>
                <MERGE2 min_interval="10000" max_interval="20000"/>
                <FD shun="true" up_thread="true" down_thread="true" />
                <FD_SOCK/>
                <VERIFY_SUSPECT timeout="1500"
                    up_thread="false" down_thread="false"/>
                <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
                    max_xmit_size="8192" up_thread="false" down_thread="false" discard_delivered_msgs="true"/>
                <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
                    down_thread="false"/>
                <pbcast.STABLE desired_avg_gossip="20000"
                    up_thread="false" down_thread="false"/>
                <FRAG frag_size="8192"
                    down_thread="false" up_thread="false"/>
                <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
                    shun="true" print_local_addr="true"/>
                <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
            
        
       
        true
        <!--
            The max amount of time (in milliseconds) we wait until the
            initial state (ie. the contents of the cache) are retrieved from
            existing members in a clustered environment
        -->
        50000
      
        
            
                <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
                false
                <!-- comma delimited FQNs to preload -->
                /
                <!-- are the cache loaders shared in a cluster? -->
                true

                <!-- we can now have multiple cache loaders, which get chained -->
                <!-- the 'cacheloader' element may be repeated -->
                
                    org.jboss.cache.loader.JDBCCacheLoader
                    <!-- same as the old CacheLoaderConfig attribute -->
                    
                        cache.jdbc.table.name=TPFCoSProvCache
    				cache.jdbc.table.create=false
    				cache.jdbc.table.drop=false
    				cache.jdbc.fqn.column=fqn
    				cache.jdbc.fqn.type=varchar(500)
    				cache.jdbc.node.column=node
    				cache.jdbc.node.type=blob
    				cache.jdbc.parent.column=parent
    				cache.jdbc.driver=oracle.jdbc.OracleDriver
    				cache.jdbc.url=jdbc:oracle:thin:@192.168.100.9:1521:TPFDB
    				cache.jdbc.user=tpf
    				cache.jdbc.password=tpf
    				cache.jdbc.datasource=tpfDBDS
                    
                    <!-- whether the cache loader writes are asynchronous -->
                    false
                    <!-- only one cache loader in the chain may set fetchPersistentState to true.
                        An exception is thrown if more than one cache loader sets this to true. -->
                    true
                    <!-- determines whether this cache loader ignores writes - defaults to false. -->
                    false
                    <!-- if set to true, purges the contents of this cache loader when the cache starts up.
                    Defaults to false.  -->
                    false
                
            
        
    


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140779#4140779

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140779