[Logo] Terracotta Discussion Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
[Expert]
JGroup Ehcache Tomcat The cluster start problem  XML
Forum Index -> Ehcache
Author Message
ystyle

neo

Joined: 08/13/2014 01:00:43
Messages: 1
Offline

In a recent study of Ehcache cluster

Because in JGroups multicast configuration can reduce the configuration file

Don't need to every machine in a configuration file, and let cluster automatically discover yourself

Do the pure Java console when the demo is ok, can enable the normal

The demo (https://github.com/ystyle/EhCacheDemo can be downloaded here)

But the development of the product is based on the development of the third party platform development, the underlying tomcat is modified

At startup platform to configure IP (not sure how binding)

Problems arise in this, because jdk1.6 jgroup, Ehcache does not support ipv6

Code:
WARN  09-07 17:38:04,762 - failed to join /ff0e:0:0:0:0:0:75:75:7500 on net0: ja
 va.net.SocketException: error setting options
 2014-7-9 17:38:07 net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerPro
 vider init
 信息: JGroups Replication started for 'CacheDemos'. JChannel: local_addr=YSTYLE-7984
 


Start is to be able to start, but could not find the other machines, local area network (LAN)
If use the JVM startup parameters disable ipv6 - Djava.net.preferIPv4Stack=true
Because IP were used for the platform (I guess platform can be directly binding the IP),
Can't find the available IP ehcache startup, a null pointer exception directly

Code:
 2014-7-8 11:52:42 net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerPro
 vider init
 严重: Failed to connect to JGroups cluster 'CacheDemos', replication will not functio
 n. JGroups properties:
 UDP(mcast_addr=231.12.21.132;mcast_port=45566;)ING:MERGE2:FD_SOCK:VERIFY_SUSPE
 CT:pbcast.NAKACK:UNICAST:pbcast.STABLE:FRAG:pbcast.GMS
 java.lang.NullPointerException
         at java.net.NetworkInterface.getInterfaceAddresses(NetworkInterface.java
 :133)
         at org.jgroups.stack.DiagnosticsHandler.bindToInterfaces(DiagnosticsHand
 ler.java:213)
         at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:87
 )
         at org.jgroups.protocols.TP.start(TP.java:1215)
         at org.jgroups.protocols.UDP.start(UDP.java:232)
         at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:952)
         at org.jgroups.JChannel.startStack(JChannel.java:864)
         at org.jgroups.JChannel._preConnect(JChannel.java:527)
         at org.jgroups.JChannel.connect(JChannel.java:284)
         at org.jgroups.JChannel.connect(JChannel.java:275)
         at net.sf.ehcache.distribution.jgroups.JGroupsCacheManagerPeerProvider.i
 nit(JGroupsCacheManagerPeerProvider.java:154)
         at net.sf.ehcache.CacheManager.doInit(CacheManager.java:472)
         at net.sf.ehcache.CacheManager.init(CacheManager.java:388)
         at net.sf.ehcache.CacheManager.<init>(CacheManager.java:264)
         at net.sf.ehcache.CacheManager.newInstance(CacheManager.java:1079)
         at net.sf.ehcache.CacheManager.newInstance(CacheManager.java:975)
 


I want to know should how to solve this problem
 
Forum Index -> Ehcache
Go to:   
Powered by JForum 2.1.7 © JForum Team