TCP Lateral Cache - Nodes unaware of one another

[Hans Liebenberg <ha...@cambrient.com>]

Hi,

Using TCP Lateral Cache. I am not sure if it has something to with order 
of startup but one node (node A) in my tcp lateral cache seems to be 
sending notifications to the other one (node B) but not the other way 
around, almost as if node B seems unaware of node A. They both have the 
same config and the behavior is erratic. If one node goes down and then 
comes back up again, surely there is some sort of background thread 
continually "pinging" the other nodes etc?

Node A config (tcp part only):

jcs.auxiliary.LTCP=org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory
jcs.auxiliary.LTCP.attributes=org.apache.jcs.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes
jcs.auxiliary.LTCP.attributes.TcpServers=192.168.0.69:1118
jcs.auxiliary.LTCP.attributes.TcpListenerPort=1118

jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=false

jcs.auxiliary.LTCP.attributes.Receive=true
jcs.auxiliary.LTCP.attributes.AllowGet=false
jcs.auxiliary.LTCP.attributes.FilterRemoveByHashCode=false


Node B config (tcp part only):

jcs.auxiliary.LTCP=org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory
jcs.auxiliary.LTCP.attributes=org.apache.jcs.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes
jcs.auxiliary.LTCP.attributes.TcpServers=192.168.0.51:1118
jcs.auxiliary.LTCP.attributes.TcpListenerPort=1118

jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=false

jcs.auxiliary.LTCP.attributes.Receive=true
jcs.auxiliary.LTCP.attributes.AllowGet=false
jcs.auxiliary.LTCP.attributes.FilterRemoveByHashCode=false


Anyone else experienced similar behavior?




---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org