自拍偷在线精品自拍偷,亚洲欧美中文日韩v在线观看不卡

Springboot實(shí)現(xiàn)Rabbitmq死信隊(duì)列以及延遲隊(duì)列的優(yōu)化

開發(fā) 前端
由于特定原因?qū)е玛?duì)列中的消息不能被消費(fèi),這樣的消息如果沒有后續(xù)處理就可以放入死信隊(duì)列中,例如一個(gè)訂單如果超時(shí)未被支付從而自動(dòng)失效,就將這個(gè)訂單放到死信隊(duì)列中。

導(dǎo)入依賴:

后續(xù)延遲隊(duì)列優(yōu)化用Springboot整合,先理解死信隊(duì)列

<!--RabbitMQ依賴-->
        <dependency>
            <groupId>com.rabbitmq</groupId>
            <artifactId>amqp-client</artifactId>
            <version>5.12.0</version>
        </dependency>

死信隊(duì)列

由于特定原因?qū)е玛?duì)列中的消息不能被消費(fèi),這樣的消息如果沒有后續(xù)處理就可以放入死信隊(duì)列中,例如一個(gè)訂單如果超時(shí)未被支付從而自動(dòng)失效,就將這個(gè)訂單放到死信隊(duì)列中。(死信隊(duì)列中的消息是可以被消費(fèi)的)

死信隊(duì)列產(chǎn)生的原因

消息TTL過期

就是在規(guī)定的時(shí)間內(nèi)消息沒有被消費(fèi),(和延遲隊(duì)列不同,延遲隊(duì)列時(shí)表示到達(dá)時(shí)間消息才可以被消費(fèi))

在生產(chǎn)者代碼中設(shè)置消息過期時(shí)間:

//生產(chǎn)者發(fā)送消息,將消息設(shè)置為TTL消息
        AMQP.BasicProperties properties =
                new AMQP.BasicProperties().builder().expiration("10000").build();

修改隊(duì)列參數(shù)argument的特殊屬性:

arguments.put("x-dead-letter-exchange", EXCHANGE_DIRECT_DEAD);//死信交換機(jī)
arguments.put("x-dead-letter-routing-key", "routingkey_direct-dead");//死信rotingkey
arguments.put("x-message-TTL", 10000);//設(shè)置過期時(shí)間(單位毫秒)  
//將死信交換機(jī)與死信隊(duì)列綁定

模擬代碼:

消費(fèi)者1

public class Consumer01 {
    public static final String EXCHANGE_DIRECT = "exchange_direct";//普通交換機(jī)的名稱
    public static final String EXCHANGE_DIRECT_DEAD = "exchange_direct_dead";//死信交換機(jī)的名稱
    public static final String QUEUE_PLAIN = "queue_plain";//普通隊(duì)列的名稱
    public static final String QUEUE_PLAIN_DEAD = "queue_plain_dead";//死信隊(duì)列的名稱
    public static void main(String[] args) throws IOException, TimeoutException, InterruptedException {
        Channel channel = RabbitMqUtils.createChannel();
        //聲明死信交換機(jī)和普通交換機(jī)
        channel.exchangeDeclare(EXCHANGE_DIRECT, BuiltinExchangeType.DIRECT);
        channel.exchangeDeclare(EXCHANGE_DIRECT_DEAD, BuiltinExchangeType.DIRECT);
        //聲明普通隊(duì)列(綁定普通隊(duì)列與死信交換機(jī)的關(guān)系,在通過rotingkey綁定死信隊(duì)列
        Map<String, Object> arguments = new HashMap<>();
        arguments.put("x-dead-letter-exchange", EXCHANGE_DIRECT_DEAD);//死信交換機(jī)
        arguments.put("x-dead-letter-routing-key", "routingkey_direct-dead");//死信rotingkey
        //設(shè)置過期時(shí)間(單位毫秒)
        arguments.put("x-message-TTL", 10000);
        channel.queueDeclare(QUEUE_PLAIN, false, false, false, arguments);
        //聲明死信隊(duì)列
        channel.queueDeclare(QUEUE_PLAIN_DEAD, false, false, false, null);
        //普通交換機(jī)和隊(duì)列的綁定
        channel.queueBind(QUEUE_PLAIN, EXCHANGE_DIRECT, "routingkey_direct");
        //死信交換機(jī)和死信隊(duì)列的綁定
        channel.queueBind(QUEUE_PLAIN_DEAD, EXCHANGE_DIRECT_DEAD, "routingkey_direct-dead");
        //模擬超時(shí)時(shí)間消息未被消費(fèi)
        Thread.sleep(1000000);
        channel.basicConsume(QUEUE_PLAIN, true, (consumerTag, message) -> {
            System.out.println("Consumer01.main接受到消息:" + new String(message.getBody()));
        }, (consumerTag, sig) -> {
        });
    }
}

生產(chǎn)者

public class Produce {
    public static void main(String[] args) throws IOException, TimeoutException {
        Channel channel = RabbitMqUtils.createChannel();
        //生產(chǎn)者發(fā)送消息,將消息設(shè)置為TTL消息
        AMQP.BasicProperties properties =
                new AMQP.BasicProperties().builder().expiration("10000").build();

        for (int i = 0; i < 10; i++) {
            String message = i + "";
            channel.basicPublish(Consumer01.EXCHANGE_DIRECT,"routingkey_direct",properties,message.getBytes(StandardCharsets.UTF_8));

        }

    }
}

消費(fèi)者2

public class Consumer2 {
    public static void main(String[] args) throws IOException, TimeoutException {
        Channel channel = RabbitMqUtils.createChannel();
        channel.basicConsume(Consumer01.QUEUE_PLAIN_DEAD, true, (consumerTag, message) -> {
            System.out.println("Consumer2.main接受死信隊(duì)列的消息:" + new String(message.getBody()));
        }, (consumerTag, sig) -> {
        });

    }
}
/**輸出結(jié)果:
Consumer2.main接受死信隊(duì)列的消息:0
Consumer2.main接受死信隊(duì)列的消息:1
Consumer2.main接受死信隊(duì)列的消息:2
Consumer2.main接受死信隊(duì)列的消息:3
Consumer2.main接受死信隊(duì)列的消息:4
Consumer2.main接受死信隊(duì)列的消息:5
Consumer2.main接受死信隊(duì)列的消息:6
Consumer2.main接受死信隊(duì)列的消息:7
Consumer2.main接受死信隊(duì)列的消息:8
Consumer2.main接受死信隊(duì)列的消息:9
    */

隊(duì)列達(dá)到了最大長度

將RabbiMQ的隊(duì)列的argument屬性的鍵設(shè)置為 x-max-length 表示隊(duì)列可以容納的最大條數(shù)

消息被拒絕

將自動(dòng)應(yīng)答設(shè)為false

在消費(fèi)者調(diào)一個(gè)Channel.basicReject,設(shè)置參數(shù)requeue為false,表示不重新排隊(duì),將消息丟到死信隊(duì)列

延遲隊(duì)列優(yōu)化

延遲隊(duì)列就是講一個(gè)消息延遲發(fā)送,例如消息在隊(duì)列中10s后才能被取出,可以通過RabbitMQ的插件或者死信隊(duì)列來實(shí)現(xiàn)

用死信隊(duì)列實(shí)現(xiàn)延遲隊(duì)列的思路:

在于死信隊(duì)列綁定的普通隊(duì)列不設(shè)置消費(fèi)者,利用TTL延遲消息,當(dāng)TTL時(shí)間過期后,到達(dá)死信隊(duì)列被消費(fèi)這樣就形成一個(gè)延遲隊(duì)列。

延遲隊(duì)列的使用場景:①典型的就是流量削峰,對于不重要的消息,可以延遲消費(fèi),有助于減輕數(shù)據(jù)庫的壓力,強(qiáng)化分布式系統(tǒng)的高可用和并發(fā)性能。②還可以實(shí)現(xiàn)一個(gè)消息提醒,例如用戶三天未登錄發(fā)送一個(gè)消息提醒。

在實(shí)際生產(chǎn)中可能存在很多不同的延遲時(shí)間要求,不可能每一個(gè)延遲要求就創(chuàng)造一個(gè)隊(duì)列,我們可以用生產(chǎn)者實(shí)現(xiàn)延遲信息,而隊(duì)列不設(shè)置TTL就可以根據(jù)生產(chǎn)的延遲消息進(jìn)行延遲發(fā)送。

但是此方法雖然實(shí)現(xiàn)了一個(gè)隊(duì)列就可以轉(zhuǎn)發(fā)不同延時(shí)時(shí)間的消息,但是有缺陷,隊(duì)列中的消息是排隊(duì)發(fā)送的,也就是說如果我第一條消息發(fā)送20s延時(shí),接著第二條消息發(fā)送2s延時(shí)。最后卻是20s消息先消費(fèi),而2s消息后消費(fèi),因?yàn)镽abbitMQ在檢測一條消息時(shí)發(fā)生了20s的阻塞。如下:

###
GET http://localhost:8080/ttl/sendExpirationMessage/aaaaa/20000
###
GET http://localhost:8080/ttl/sendExpirationMessage/bbbbb/2000
最后輸出結(jié)果是先消費(fèi)aaaa后消費(fèi)bbbb

可以通過RabbitMQ的插件實(shí)現(xiàn)延時(shí)隊(duì)列,此方法沒有這缺陷

從官網(wǎng)上下載對應(yīng)版本的延遲插件,下載后如圖:交換機(jī)類型會(huì)多出一個(gè) x-delayed-message


在我們自定義的交換機(jī)中,這是一種新的交換機(jī)類型,該類型消息支持延遲投遞機(jī)制,消息傳遞后并不會(huì)立即投遞到目標(biāo)隊(duì)列中,而是存儲在mnesia(一個(gè)分布式數(shù)據(jù)系統(tǒng))表中,當(dāng)達(dá)到投遞時(shí)間時(shí),才會(huì)投遞到目標(biāo)隊(duì)列中。

代碼實(shí)例:

配置類:

@Configuration
public class RabbitDelayedConfig {
    //延遲交換機(jī)
    public static final String DELAYED_EXCHANGE = "delayed.exchange";
    //延遲隊(duì)列b
    public static final String DELAYED_QUEUE = "delayed.queue";
    //延遲交換機(jī)和隊(duì)列的routingkey
    public static final String DELAYED_ROTINGKEY = "delayed.routingkey";

    //public CustomExchange(String name, String type, boolean durable, boolean autoDelete, Map<String, Object> arguments) {
    //		super(name, durable, autoDelete, arguments);
    //		this.type = type;
    //	}
    @Bean
    public CustomExchange delayedExchange() {
        Map<String, Object> arguments = new HashMap<>();
        //定義延遲消息類型由那種交換機(jī)規(guī)則處置
        arguments.put("x-delayed-type", "direct");
        return new CustomExchange(DELAYED_EXCHANGE, "x-delayed-message", false, false, arguments);
    }

    @Bean
    public Queue delayedQueue() {
        return QueueBuilder
                .nonDurable(DELAYED_QUEUE)
                .build();
    }

    @Bean
    public Binding delayedBinding() {
        return BindingBuilder.bind(delayedQueue()).to(delayedExchange()).with(DELAYED_ROTINGKEY).noargs();

    }
}

生產(chǎn)者:

/*延遲交換機(jī)發(fā)送消息*/
    @GetMapping("/sendDelayedMessage/{message}/{delayedTTL}")
    public void sendDelayedMessage(@PathVariable String message, @PathVariable Integer delayedTTL) {
        log.info("當(dāng)前時(shí)間:{},發(fā)送一條延遲時(shí)間為{}的延遲消息給延遲隊(duì)列:{}", new Date().toString(), delayedTTL, message);
        rabbitTemplate.convertAndSend(RabbitDelayedConfig.DELAYED_EXCHANGE,
                RabbitDelayedConfig.DELAYED_ROTINGKEY,
                message,
                msg -> {
                    msg.getMessageProperties().setDelay(delayedTTL);//設(shè)置消息的延遲消息時(shí)間
                    return msg;
                });
    }

消費(fèi)者:

@Slf4j
@Component
public class DelayedQueueConsumer {

    @RabbitListener(queues = RabbitDelayedConfig.DELAYED_QUEUE)
    public void queue(Message message) {
        log.info("接受到延遲隊(duì)列的消息,當(dāng)前時(shí)間:{},消息:{}",new Date().toString(),new String(message.getBody()));
    }
}
責(zé)任編輯:武曉燕 來源: 今日頭條
相關(guān)推薦

2023-04-27 07:43:22

RabbitMQ重試隊(duì)列死信隊(duì)列

2023-09-05 15:48:14

RabbitMQ延遲隊(duì)列

2024-04-15 00:00:00

RabbitMQ死信隊(duì)列消息

2024-03-18 00:00:03

RabbitMQ代碼延遲隊(duì)列

2023-08-08 08:28:03

消息消費(fèi)端Spring

2024-04-19 00:47:07

RabbitMQ消息機(jī)制

2024-12-25 09:32:06

2023-10-23 10:02:58

RabbitMQ延遲隊(duì)列

2021-12-08 10:47:35

RabbitMQ 實(shí)現(xiàn)延遲

2024-04-28 08:52:33

RabbitMQ延遲隊(duì)列延遲插件

2024-01-26 13:16:00

RabbitMQ延遲隊(duì)列docker

2023-11-03 10:33:26

2021-10-15 10:39:43

RabbitMQ隊(duì)列延遲

2024-10-16 09:29:30

RabbitMQ延遲隊(duì)列

2024-11-05 16:58:21

RabbitMQ訂單超時(shí)取消延遲隊(duì)列

2024-05-08 14:49:22

Redis延遲隊(duì)列業(yè)務(wù)

2024-07-16 18:05:19

延遲隊(duì)列MQRabbitMQ

2025-02-19 00:00:00

RabbitMQTTL插件

2018-07-20 09:16:04

鏈?zhǔn)?/a>存儲結(jié)構(gòu)

2020-07-30 08:03:36

MQ死信隊(duì)列
點(diǎn)贊
收藏

51CTO技術(shù)棧公眾號