Spring-Retry

I have the following two cases In case of ExceptionA : retrying for finite number of times and finally when number of retrials exhausted, message is written in a dead letter queue In case of ExceptionB : simply, message should be written to dead letter queue I want to support the two cases on the same listener container factory and the same queue. I already have the following configuration to support case 1 successfully: @Bean public RetryOperationsInterceptor workMessagesRetryInterceptor() { return RetryInterceptorBuilder.stateless() .maxAttempts(5) .backOffOptions(1000, 2, 10000) .recoverer

If I have a method that has a Spring retryable for a certain exception, and also has a Transactional(Requires_new), every time the retry is done, will it create a new transaction or use the existing one? ie @Retryable(maxAttempts = 5, backoff = @Backoff(delay = 250), include = {ActivitiOptimisticLockingException.class}) @Transactional(propagation = Propagation.REQUIRES_NEW) public void setVariable(String processId, String variableName, String variableValue){ engine.getRuntimeService().setVariable(processId, variableName, variableValue); } What will actually happen here? will be created new

I have a spring managed bean of type B. I have @EnableREtry in a @Configuration class. When I use @Retryable on doStuff() , the method gets retried on failure as expected. But, the method I really want to retry is a method defined in the base class, A. A is a concrete class and not a spring managed bean. the doSomethingElse method doesn't get retried on throwing an exception. I really want doSomethingElse to be retried, the base class method. However, I'm not sure how to do this. I'm guessing it's because A is a concrete class and not a bean, although it does serve as a base class. Do I need

I've got a spring integration pipeline and I've got a number of different service activators that I want to enable retry for. I want to use the same retry policy (i.e. the number of retries, back-off policy, etc). Can I just have one bean that implements the retry policy and use it for several different service activators, or does each service activator need its own retry bean? In other words, can I just make one bean "retryWithBackupAdviceSession" and set it the request-hadler-advice-chain for several service activators? Or does each one need its own? Here's an example of the retry policy I'm

Spring-retry 该项目为Spring应用程序提供声明式重试支持，它用于Spring Batch、Spring Integration、Apache Hadoop的Spring（以及其他），命令式重试也支持显式使用。 入门 声明式示例 @Configuration @EnableRetry public class Application { @Bean public Service service() { return new Service(); } } @Service class Service { @Retryable(RemoteAccessException.class) public void service() { // ... do something } @Recover public void recover(RemoteAccessException e) { // ... panic } } 调用 service 方法，如果它由于 RemoteAccessException 失败，那么它将重试（默认情况下最多三次），如果继续失败，则执行 recover 方法， @Retryable 注解属性中有各种选项，用于包含和排除异常类型、限制重试次数和回退策略。 使用上面显示的 @Retryable