简体   繁体   中英

Ehcache JGroups Tcp replication error:dropped message from xxx(not in xmit_table)

Used jar version:
ehcache-core:2.4.2 
ehcache-jgroupsreplication:1.4(exclusion ehcache-core)

I have two servers, one is 192.168.6.84 and another is 192.168.6.83, and my configuration is:

<cacheManagerPeerProviderFactory propertySeparator="::" 
 properties="connect=TCP(bind_addr=192.168.6.84;bind_port=7800): 
TCPPING(initial_hosts=192.168.6.83[7800],192.168.6.84[7800];port_range=10;
   timeout=3000; num_initial_members=2): 
VERIFY_SUSPECT(timeout=1500): 
pbcast.NAKACK(use_mcast_xmit=false;gc_lag=100;retransmit_timeout=3000;
   discard_delivered_msgs=false): 
pbcast.GMS(join_timeout=5000;print_local_addr=false)" class="net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerProviderFactory"/>

And another configuration only change the ip address. And in my test code, I do only one thing:

  • one server A always put element in cache per 2 seconds,
  • another server B always get cache's size per 2 seconds

B's cache size is always 0 and it warns:

NAKACK.java:794 -- xxxx(B's computer name):dropped message from xxxx(A's computer name) (not in xmit_table),keys are xxxxx,view =[xxxx|0]

Is it my configuration error?

First off, your configuration looks odd: you're missing UNICAST, any failure detection protocol (FD_ALL, FD_SOCK), and STABLE. Absence of the latter means you'll eventually run out of memory as messages to the entire cluster are not purged!

The error you're seeing means that the cluster has not formed.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM