Dubbo Installation Configuration Considerations

Dubbo Installation Configuration Considerations

Reference url:http://blog.csdn.net/lichunan/article/details/40349645

======

Management side:

Remember to change the port number of Tomcat, otherwise it will conflict with the monitor 8080 (how to deploy on the same machine)

Dubbo.properties file
dubbo.registry.address=zookeeper://x.x.x.x:2181
dubbo.admin.root.password= Users
dubbo.admin.guest.password= Password

=============

Monitoring side:

Dubbo.properties file

Dubbo.container=log4j,spring,registry,jetty
Dubbo.application.name=simple-monitor
Dubbo.application.owner=
#dubbo. registry.address=multicast://224.5.6.7:1234
#dubbo. registry.address=zookeeper://127.0.0.1:2181
#dubbo. registry.address=redis://127.0.0.1:6379
#dubbo. registry.address=dubbo://127.0.0.1:9090
dubbo.registry.address=zookeeper://x.x.x.x:2181
dubbo.protocol.port=7070
dubbo.jetty.port=8080
Dubbo.jetty.directory=${user.home}/monitor
Dubbo.charts.directory=${dubbo.jetty.directory}/charts
Dubbo.statistics.directory=${user.home}/monitor/statistics
Dubbo.log4j.file=logs/dubbo-monitor-simple.log
Dubbo.log4j.level=warn

In the installation, the small Jiao classmate encountered a monster problem, that is, the monitoring side may only be in JDK1.8 above the version to start, on the JDK1.7 start, always say what monitor process has been started, and then stopped.

I just commented on the relevant shell.

I don't know if it's right.

if[-Z"$SERVER _name"]; Thenserver_name=`hostname`fi#PIDS = ' ps-f | grep java | grep ' $CONF _dir ' |awk ' {print $} ' #if [-n ' $PIDS ']; then# echo "Error:the $SERVER _na ME already started! " # echo "PID: $PIDS" # Exit 1#fiif[-N"$SERVER _port"]; ThenServer_port_count= ' Netstat-tln |grep$SERVER _port |WC-l 'if[$SERVER _PORT_COUNT-GT0]; Then        Echo "error:the $SERVER _name Port $SERVER _port already used!"Exit1    fifi

Dubbo Installation Configuration Considerations