JBoss Ehcache复制异常(在xmit_table中找不到发件人) [英] JBoss Ehcache Replication Exception (sender not found in xmit_table)
问题描述
因此，我只是在apache后面设置了两个jboss节点，启用了集群并设置了ehcache同步.现在，两个节点都在运行，我在未收到请求的节点上收到以下异常:
So, I just setup two jboss nodes behind apache, enabled clustering and setup ehcache synchronization. Now with both nodes running, I get the following exception on the node that did not receive the request:
...
JBoss_5_1_0_GA date=200905221634)] Started in 2m:16s:391ms
12:52:51,139 ERROR [NAKACK] sender 10.166.17.53:7600 not found in xmit_table
12:52:51,139 ERROR [NAKACK] range is null
12:52:51,145 INFO [RPCManagerImpl] Received new cluster view: MergeView::[10.16 6.17.52:7600|1] [10.166.17.52:7600, 10.166.17.53:7600], subgroups=[[10.166.17.52 :7600|0] [10.166.17.52:7600], [10.166.17.53:7600|0] [10.166.17.53:7600]]
12:53:10,006 WARN [NAKACK] 10.166.17.52:7600] discarded message from non-member 10.166.17.53:7600, my view is [10.166.17.52:7600|0] [10.166.17.52:7600]
12:53:10,108 WARN [NAKACK] 10.166.17.52:7600] discarded message from non-member 10.166.17.53:7600, my view is [10.166.17.52:7600|0] [10.166.17.52:7600]
12:53:10,110 ERROR [NAKACK] sender 10.166.17.53:7600 not found in xmit_table
12:53:10,110 ERROR [NAKACK] range is null
12:53:10,113 INFO [graCluster] New cluster view for partition graCluster (id: 1 , delta: 1) : [127.0.0.1:1099, 127.0.0.1:1099]
12:53:10,117 INFO [graCluster] Merging partitions...
12:53:10,118 INFO [graCluster] Dead members: 0
12:53:10,120 INFO [graCluster] Originating groups: [[10.166.17.52:7600|0] [10.1 66.17.52:7600], [10.166.17.53:7600|0] [10.166.17.53:7600]]
以下是我的ehcache.xml的样子:
Following is what my ehcache.xml looks like:
<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerProviderFactory"
properties="connect=TCP(start_port=7800):TCPPING(initial_hosts=10.46.49.52[7800],10.46.49.53[7800];port_range=10;timeout=3000;
num_initial_members=2;up_thread=true;down_thread=true):
VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false):
pbcast.NAKACK(down_thread=true;up_thread=true;gc_lag=100;retransmit_timeout=3000):
pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;
print_local_addr=false;down_thread=true;up_thread=true)"
propertySeparator="::"/>
最后，这是我运行两个节点的方式:
Finally this is how I run both the nodes:
./run.sh -c全部-g myCluster -Djboss.default.jgroups.stack = tcp -Djgroups.tcpping.initial_hosts = 10.166.17.52 [7600]，10.166.17.53 [7600] -Djboss.messaging.ServicePeerId = 1 -Djgroups.bind_addr = 10.166.17.52 -Djboss.node.name = node1 -b 0.0.0.0
./run.sh -c all -g myCluster -Djboss.default.jgroups.stack=tcp -Djgroups.tcpping.initial_hosts=10.166.17.52[7600],10.166.17.53[7600] -Djboss.messaging.ServicePeerId=1 -Djgroups.bind_addr=10.166.17.52 -Djboss.node.name=node1 -b 0.0.0.0
和
./run.sh -c全部-g myCluster-Djboss.default.jgroups.stack = tcp -Djgroups.tcpping.initial_hosts = 10.166.17.52 [7600]，10.166.17.53 [7600] -Djboss.messaging.ServicePeerId = 2 -Djgroups.bind_addr = 10.166.17.53 -Djboss.node.name = node2 -b 0.0.0.0
./run.sh -c all -g myCluster-Djboss.default.jgroups.stack=tcp -Djgroups.tcpping.initial_hosts=10.166.17.52[7600],10.166.17.53[7600] -Djboss.messaging.ServicePeerId=2 -Djgroups.bind_addr=10.166.17.53 -Djboss.node.name=node2 -b 0.0.0.0
服务器正在尝试互相通信.我不确定它们是否位于同一群集中.任何帮助将不胜感激.
The servers are trying to talk to each other. I am not sure whether they are even in the same cluster or not. Any help will be much appreciated.
推荐答案
我打开了ehcache日志记录，并发现尽管节点尝试彼此通信，但它们失败了，无法建立彼此的连接.通过修复配置错误的主机文件，可以解决此问题.节点开始互相交谈后，ehcache复制就起作用了.显然，有关xmit_table的错误是无关紧要的.
I turned on ehcache logging and figured out that although the nodes attempt to talk to each other, they fail and could not establish connection to each other. This was resolved by fixing a badly configured host file. Once the nodes started talking to each other, ehcache replication worked. Apparently the error about xmit_table was inconsequential.
这篇关于JBoss Ehcache复制异常(在xmit_table中找不到发件人)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
