Idempotent Consumer 3

最新推荐文章于 2025-04-16 17:42:20 发布

转载最新推荐文章于 2025-04-16 17:42:20 发布 · 568 阅读

文章标签：

#idempotent #duplicates #exchange #filter #header #junit

Java 同时被 2 个专栏收录

53 篇文章

订阅专栏

camel

36 篇文章

订阅专栏

本文介绍幂等消费者模式的实现原理及使用方法，该模式通过过滤重复消息来确保消息仅被消费一次。文章详细解释了如何配置和使用Camel中的IdempotentConsumer组件，并提供了基于内存和JPA的不同实现方式。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The Idempotent Consumer![][5] from the EIP patterns is used to filter out duplicate messages. 



This pattern is implemented using the IdempotentConsumer![][5] class. This uses an Expression to calculate a unique message ID string for a given message exchange; this ID can then be looked up in the MessageIdRepository![][5] to see if it has been seen before; if it has the message is consumed; if its not then the message is processed and the ID is added to the repository.



The Idempotent Consumer essentially acts like a Message Filter to filter out duplicates.



Camel will add the message id eagerly to the repository to detect duplication also for Exchanges currently in progress.  

> On completion Camel will remove the message id from the repository if the Exchange failed, otherwise it stays there.<p> 



### Options



The Idempotent Consumer has the following options:



Option  Default  Description 



eager 

true 

**Camel 2.0:** Eager controls whether Camel adds the message to the repository before or after the exchange has been processed. If enabled before then Camel will be able to detect duplicate messages even when messages are currently in progress. By disabling Camel will only detect duplicates when a message has successfully been processed. 



**Using the Fluent Builders**



The following example will use the header **myMessageId** to filter out duplicates

    

    RouteBuilder builder = new RouteBuilder() {

        public void configure() {

            errorHandler(deadLetterChannel("mock:error"));

    

            from("seda:a").idempotentConsumer(header("myMessageId"), MemoryIdempotentRepository.memoryIdempotentRepository(200))

                .to("seda:b");

        }

    };



The above example![][5] will use an in-memory based MessageIdRepository![][5] which can easily run out of memory and doesn't work in a clustered environment. So you might prefer to use the JPA based implementation which uses a database to store the message IDs which have been processed

    

    from("direct:start").idempotentConsumer(

            header("messageId"),

            jpaMessageIdRepository(lookup(JpaTemplate.class), PROCESSOR_NAME)

    ).to("mock:result");



In the above example![][5] we are using the header **messageId** to filter out duplicates and using the collection **myProcessorName** to indicate the Message ID Repository to use. This name is important as you could process the same message by many different processors; so each may require its own logical Message ID Repository.



For further examples of this pattern in use you could look at the junit test case![][5]



#### Using This Pattern



If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.



![][21]