当前位置：网站首页>SZT Mr message middleware is easy to use

routine http perhaps socket request , After the service provider receives the request , Add a new thread or use an existing idle thread , Start using server resources , Start asking for consumption ;

once tps Surge , When the current number of threads on the server is insufficient , Thread switching , Use server resources together , Competing for resources , Use under high pressure , But pay attention to , Even if the server can withstand , Due to each request , Competing threads , It also leads to long response times , Or a timeout , The user experience is not good either .

And the message queue , Ask to go in , Because it's a queue , fifo , All requests are queued inside , Each request can set the waiting time in the queue （ Destroy request if exceeded ）;

The server can get requests from the queue at a fixed speed , Ensure the speed of the server portal , Here we are. , It feels like a current limiting strategy ,

notes ： Get requests from the queue at a fixed rate ：

For example, after the server gets a request from the message queue , After consumption, return the message ,10ms After that, I won a request （ If you can't get it, you won't spend it ）.

One ： Simple understanding mr The concept

mr Our common name is , Generally, it is also called Shenzhen Zhengtong messaging middleware , It's a program , Deployed in the server , After startup , follow-up , Yours Java Services can be started from this exe In the program , Get the corresponding request information ;

According to the elder's explanation , This is the message passing middleware for most securities companies and banks , A complete request process ,

Broker side program --》 brokers mr -- > Shenzheng Tongzhong --》 Service charge mr -->Java Gateway Program

notes ： Whether it's a broker side program or java Gateway Program , Through a series of api, receive mr The request inside , Go to mr Send a request inside , And check whether the current connection is normal , Automatic reconnection and other operations ;

Documents provided on the official website of szcst , Also have demo, Watch how to operate these api

1. An official document , Stress mr Relevant concepts , install 、 Operations etc.

2. One copy java api Operation document , And a simple demo, Secondly, the government has qq Group ,api There is something wrong with the operation , You can also contact , It's really convenient

After installation ,

Two ： Login mode

Remote desktop login

for example , according to ip And username and password

entry ,IP, Account and password , After login , go in

3、 ... and ： Directory structure

3.1bsmr：

ini When you file mr Configuration of

The configuration file has relevant comments , You can refer to the configuration , You can also contact Shenzhen Zhengtong technology teacher for support ;

log Log files

bsmr Local time mr Log of connection hub and related scheduled inspection ;

sxdata yes , Relevant logs of requests , Configure the refurbishment policy of the log file according to the configuration file

3.2mxterm

Below exe A program is a client startup program , Do not start or affect the transaction

Four ： start-up 、 Check mr Is the configuration successful?

4.1 Background start ,

bsmr Under the folder ,bsmr.exe Just start the program , This program and mr The central link

4.2 Client startup check real time status

mxterm Under the table of contents , Click on exe Program

Enter the account and password configured in the configuration file , Log in

4.3 Real-time check mr state ;

You can also get it from bsmr Log check mr Connect , Just view the keywords , There is no extension here ;

a: The upper right corner of the client , Whether to display the small account number and the connected ,

No , It indicates that there is a problem with the configuration file

b: The upper left corner of the client , Check local mr Whether the connection with the central nervous system is normal , And more than one mr Whether the shared unit configuration is successful

Red , Connection hub failed

green , The connection is normal

white , Not started or failed to start

c: The lower left corner , Check local mr And the client （ Brokerage side ）mr Whether the connection is normal

green ： The connection is normal

white ： Unconnected

5、 ... and ： Routine questions

5.1mr Log analysis

for example , The broker sent it to us ,mr Will print three lines of logs ; View keywords info

1.info=recv msg,save to local bug

indicate , Local mr We have received the request from the other securities firm ;

2.info=recv away msg by linkid[89000000]

indicate , This request , Has been served by a third party （ gateway ） Take away ,89000000 You can view the upper left corner of the client , See which one ip Request for removal

3.info = switch msg to su ok

indicate , The request has been consumed by us , The return message has been sent to the hub

4. Additional remarks , If the request times out or is not taken from the queue , There will be info=deleet Destroyed logs

Then according to , Is to which stage , Judge 、 Solve it