ROCKETMQ startup steps for Windows edition clients

First, download ROCKETMQ
First, we go to download ROCKETMQ,ROCKETMQ is an open source thing, can go to github download, address is: https://github.com/alibaba/RocketMQ/releases
Go in, we will see a lot of versions, the latest is v3.2.6, is also Ali Tianchi Big Data Middleware game version, under window, we directly download the compiled version, it is OK.
namely: alibaba-rocketmq-3.2.6.tar.gz
After download Direct decompression: We will see a alibaba-rocketmq folder, this is what we need. This is actually very good to install, just need to add an environment variable on it.

Second, download the client Jar package (Rocketmq-externals-master (package name))

Specific as follows:

1, modify the configuration file, so that the management interface with the ROCKETMQ Cluster Generation Association.

Incubator-rocketmq-externals-master/rocketmq-console/src/main/resources/application.properties

Modify the content and modify the results as shown:

2. Compiling rocketmq-console

Compile command: mvn clean package-dmaven.test.skip=true (note: Do not use the MVN package directly, will prompt a lot of errors)

3. Upload the compiled jar package to the Linux server

(You can omit this step if you compile directly on the Linux environment)

I uploaded it to the local virtual machine 192.168.6.5. Path is:/home/hadmin/jar

4. Running the jar package

Command: Java-jar Target/rocketmq-console-ng-1.0.0.jar

5. Using the browser to access the management interface

Bearing Address: http://192.168.6.5:8080/

6. Problems that may be encountered

The screen can start normally, but from the monitor log on the console, there is an error log as follows.

Org.apache.rocketmq.remoting.exception.RemotingTimeoutException:wait response on the channel <192.168.1.80:10918 > Timeout, (ms)

The reason is that isvipchannel defaults to true, which monitors the VIP channel of the ROCKETMQ and sets the property to False.

The configuration file after Setup is as follows:

Server.contextpath=server.port=8080#spring.application.index=truespring.application.name= Rocketmq-consolespring.http.encoding.charset=utf-8spring.http.encoding.enabled=truespring.http.encoding.force= truelogging.config=classpath:logback.xml#if This value is empty,use env value rocketmq.config.namesrvAddr namesrv_addr | Now, your can set it in OPS Page.default localhost:9876rocketmq.config.namesrvaddr=192.168.1.80:9876;192.168.1.81:9876# If you use ROCKETMQ version < 3.5.8, Rocketmq.config.isVIPChannel should be False.default truerocketmq.config.isVIPCha Nnel=false#rocketmq-console ' s data path:dashboard/monitorrocketmq.config.datapath=/home/hadmin/data/rocketmq#set It false if you don ' t want use Dashboard.default truerocketmq.config.enabledashboardcollect=true

Three,2, add environment variables
Open the environment variable configuration of the computer, add a namesrv_addr=127.0.0.1:9876, of course, I here is nameserver and broker server on a machine, if not on a machine, it needs to be set to nameserver address.
Write a picture description here


Iv. Start-up service
1, cmd into the DOS interface
2. Switch to the ROCKETMQ directory

3. Input command: start/b mqnamesrv.exe start mqnamesrv

4. Start Mqbroker, enter command Mqbroker-n 127.0.0.1:9876

It is important to note that the boot order must start with mqnameserver and then start the broker, or it will go wrong.

This article refers to other users of the information and their own summary, reference address: http://m.blog.csdn.net/jie11447416/article/details/51810280
V. Visit: 127.0.0.1:8080

ROCKETMQ startup steps for Windows edition clients