Example usage for org.springframework.amqp.rabbit.config AbstractRetryOperationsInterceptorFactoryBean subclass-usage

Introduction

In this page you can find the example usage for org.springframework.amqp.rabbit.config AbstractRetryOperationsInterceptorFactoryBean subclass-usage.

Usage

From source file org.springframework.amqp.rabbit.config.StatelessRetryOperationsInterceptorFactoryBean.java

/**
 * Convenient factory bean for creating a stateless retry interceptor for use in a message listener container, giving
 * you a large amount of control over the behaviour of a container when a listener fails. To control the number of retry
 * attempt or the backoff in between attempts, supply a customized {@link RetryTemplate}. Stateless retry is appropriate
 * if your listener can be called repeatedly between failures with no side effects. The semantics of stateless retry
 * mean that a listener exception is not propagated to the container until the retry attempts are exhausted. When the

From source file org.springframework.amqp.rabbit.config.StatefulRetryOperationsInterceptorFactoryBean.java

/**
 * Convenient factory bean for creating a stateful retry interceptor for use in a message listener container, giving you
 * a large amount of control over the behaviour of a container when a listener fails. To control the number of retry
 * attempt or the backoff in between attempts, supply a customized {@link RetryTemplate}. Stateful retry is appropriate
 * if your listener is using a transactional resource that needs to be rollback on an exception (e.g. a stateful
 * connection to a back end server). JPA is the canonical example. The semantics of stateful retry mean that a listener