搭建dubbo+zookeeper+spring架构为什么不要用jdk1.8
1个回答
展开全部
我了zookeeper-3.4.5.tar.gz版本的包。接下来把zookeeper-3.4.5.tar.gz解压到文件夹D:\zookeeper-3.4.5\中,
然后将zoo_sample.cfg改名为zoo.cfg。然后将配置文件zoo.cfg改成如下:
[html] view plain copy
# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.
dataDir=D:\\zookeeper-3.4.5\\data
dataLogDir=D:\\zookeeper-3.4.5\\log
# the port at which the clients will connect
clientPort=2181
然后就可以启动了。
DUBBO的管理DUBBO-ADMIN的部署
dubbo-admin.war可在网上百度去,但是我了好几个war包,发布上去服务启动都报错,这个时候大概是我们系统的JDK和编译
dubbo-admin.war的JDK版本不同导致的了。所以我之后直接了dubbo-master的源代码,然后自己编译了一个war包,这样就不会存
在启动报错的问题了。
然后将zoo_sample.cfg改名为zoo.cfg。然后将配置文件zoo.cfg改成如下:
[html] view plain copy
# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.
dataDir=D:\\zookeeper-3.4.5\\data
dataLogDir=D:\\zookeeper-3.4.5\\log
# the port at which the clients will connect
clientPort=2181
然后就可以启动了。
DUBBO的管理DUBBO-ADMIN的部署
dubbo-admin.war可在网上百度去,但是我了好几个war包,发布上去服务启动都报错,这个时候大概是我们系统的JDK和编译
dubbo-admin.war的JDK版本不同导致的了。所以我之后直接了dubbo-master的源代码,然后自己编译了一个war包,这样就不会存
在启动报错的问题了。
推荐律师服务:
若未解决您的问题,请您详细描述您的问题,通过百度律临进行免费专业咨询