Receiver exception handling method, server and storage medium of message middleware

Abstract

The invention discloses a message middleware receiver exception handling method, which comprises the following steps that: after a sender sends a message to a network, the message is put into a firstshared memory, and under the action of a first asynchronous persistence component, the message is written into a disk; after receiving the message from the network, the receiver puts the message intoa second shared memory and writes the message into a disk under the action of a second asynchronous persistence component; when it is detected that a non-key slow receiver exists in the receivers, reading a message from a predetermined disk of the receiver and submitting the message to an application for processing; and when it is detected that the receiver has a fault, caching the message sent bythe sender, and stopping sending the message to the network. The invention also discloses a server and a computer readable storage medium. Under the condition that the ultra-low time delay requirement of the high-speed message middleware can be met, local faults can be avoided, and a slow receiver cannot affect the whole distributed system.

Description

technical field [0001] The present invention relates to the technical field of Internet finance, and in particular to a receiver exception handling method of message middleware, a server and a computer-readable storage medium. Background technique [0002] Message middleware uses an efficient and reliable message delivery mechanism for platform-independent message exchange, and is an important basic system for communication between application components in a distributed environment. Traditional message middleware usually has a central message server (Broker, referred to as proxy node), the message sender and receiver are connected to this proxy node, and rely on the proxy node for message distribution and fault isolation, rather than direct communication with each other . When the receiver fails, the proxy node of the message middleware will continue to receive and store messages; when the receiver recovers from the failure, the receiver can continue to receive breakpoint ...

Images