这篇博客是紧接着上篇博客来说的http://blog.youkuaiyun.com/liuchuanhong1/article/details/64126346
在上篇博客中,我们基本上实现了分布式的定时任务架构的搭建,但是,当我们异步消费消息中间件中的消息的时候,如果执行的过程中抛了异常,那么,我们无法做到消息重试,示例如下:
@Component // 必须加此注解,该类才会被作为Message Driven POJO使用
public class Consumer {
@JmsListener(destination = "mytest.queue")
@Async // 异步执行此方法
public void receiveQueue(TextMessage text) throws Exception {
throw new Exception();
}
}
测试结果如下:
console结果
2017-03-20 18:38:10.883 ERROR 6276 --- [TaskExecutor-91] .a.i.SimpleAsyncUncaughtExceptionHandler : Unexpected error occurred invoking async method 'public void com.chhliu.springboot.jms.Consumer.receiveQueue(javax.jms.TextMessage) throws java.lang.Exception'.
java.lang.Exception: null
at com.chhliu.springboot.jms.Consumer.receiveQueue(Consumer.java:15) ~[classes/:na]
at com.chhliu.springboot.jms.Consumer$$FastClassBySpringCGLIB$$68e885f7.invoke(<generated>) ~[classes/:na]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:721) ~[spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.interceptor.AsyncExecutionInterceptor$1.call(AsyncExecutionInterceptor.java:115) ~[spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_121]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_121]
ActiveMq的管理页面
我们发现入队列100条消息,出队列也是100条消息
从上面的测试中,可以看出,当我们使用异步来执行的时候,即使程序中抛出了异常,ActiveMq的消息重试机制也不会生效,那如果我们从队列中接收到消息,但是在执行程序的过程中,程序抛了异常,我们又想重试,怎么处理了?
1、不使用异步
2、使用jms自带的并发
3、使用客户端消息确认机制
JMS在默认的情况下,使用的是自动的消息确认机制,确认总是隐式的在onMessage处理器返回之后发生
在配置文件中,添加如下配置:
# 客户端,手动消息确认机制
spring.jms.listener.acknowledge-mode=CLIENT
# jms并发数
#spring.jms.listener.concurrency=6
# jms限制的最大并发数
spring.jms.listener.max-concurrency=10
首先,我们来测试并发
测试代码如下:
@Component // 必须加此注解,该类才会被作为Message Driven POJO使用
public class Consumer {
@JmsListener(destination = "mytest.queue")
// @Async // 不使用异步操作
public void receiveQueue(TextMessage text) throws Exception {
System.out.println(Thread.currentThread().getName()+":Consumer收到的报文为:"+text.getText());
text.acknowledge(); // 客户端手动消息确认机制,如果我们的程序处理正常时,需手动调用
}
}
测试结果如下:
DefaultMessageListenerContainer-5:Consumer收到的报文为:myname is chhliu!!!44
DefaultMessageListenerContainer-4:Consumer收到的报文为:myname is chhliu!!!46
DefaultMessageListenerContainer-8:Consumer收到的报文为:myname is chhliu!!!85
DefaultMessageListenerContainer-1:Consumer收到的报文为:myname is chhliu!!!42
DefaultMessageListenerContainer-7:Consumer收到的报文为:myname is chhliu!!!87
DefaultMessageListenerContainer-6:Consumer收到的报文为:myname is chhliu!!!48
DefaultMessageListenerContainer-2:Consumer收到的报文为:myname is chhliu!!!41
DefaultMessageListenerContainer-3:Consumer收到的报文为:myname is chhliu!!!49
DefaultMessageListenerContainer-10:Consumer收到的报文为:myname is chhliu!!!92
DefaultMessageListenerContainer-5:Consumer收到的报文为:myname is chhliu!!!54
DefaultMessageListenerContainer-9:Consumer收到的报文为:myname is chhliu!!!93
DefaultMessageListenerContainer-4:Consumer收到的报文为:myname is chhliu!!!56
DefaultMessageListenerContainer-8:Consumer收到的报文为:myname is chhliu!!!95
DefaultMessageListenerContainer-1:Consumer收到的报文为:myname is chhliu!!!51
DefaultMessageListenerContainer-7:Consumer收到的报文为:myname is chhliu!!!97
DefaultMessageListenerContainer-6:Consumer收到的报文为:myname is chhliu!!!58
DefaultMessageListenerContainer-2:Consumer收到的报文为:myname is chhliu!!!50
DefaultMessageListenerContainer-3:Consumer收到的报文为:myname is chhliu!!!59
我们看到,即使在没有使用异步的情况下,也可以实现异步的并发操作。
其次,我们来测试消息失败重试
测试代码如下:
@Component // 必须加此注解,该类才会被作为Message Driven POJO使用
public class Consumer {
private int num = 1;
@JmsListener(destination = "mytest.queue")
public void receiveQueue(TextMessage text) throws Exception {
System.out.println("重试次数"+num++);
System.out.println(Thread.currentThread().getName()+":Consumer收到的报文为:"+text.getText());
throw new Exception();
}
}
测试结果如下:
………………前面省略…………
重试次数5
DefaultMessageListenerContainer-4:Consumer收到的报文为:myname is chhliu!!!100
2017-03-20 19:24:18.596 WARN 5948 --- [enerContainer-4] o.s.j.l.DefaultMessageListenerContainer : Execution of JMS message listener failed, and no ErrorHandler has been set.
org.springframework.jms.listener.adapter.ListenerExecutionFailedException: Listener method 'public void com.chhliu.springboot.jms.Consumer.receiveQueue(javax.jms.TextMessage) throws java.lang.Exception' threw exception; nested exception is java.lang.Exception
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:112) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.onMessage(MessagingMessageListenerAdapter.java:69) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:721) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:681) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:651) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:317) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1166) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1158) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1055) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_121]
Caused by: java.lang.Exception: null
at com.chhliu.springboot.jms.Consumer.receiveQueue(Consumer.java:20) ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_121]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_121]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_121]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_121]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:196) ~[spring-messaging-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:113) ~[spring-messaging-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:104) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
... 10 common frames omitted
重试次数6
DefaultMessageListenerContainer-4:Consumer收到的报文为:myname is chhliu!!!100
2017-03-20 19:24:19.617 WARN 5948 --- [enerContainer-4] o.s.j.l.DefaultMessageListenerContainer : Execution of JMS message listener failed, and no ErrorHandler has been set.
org.springframework.jms.listener.adapter.ListenerExecutionFailedException: Listener method 'public void com.chhliu.springboot.jms.Consumer.receiveQueue(javax.jms.TextMessage) throws java.lang.Exception' threw exception; nested exception is java.lang.Exception
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:112) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.onMessage(MessagingMessageListenerAdapter.java:69) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:721) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:681) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:651) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:317) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1166) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1158) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1055) [spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_121]
Caused by: java.lang.Exception: null
at com.chhliu.springboot.jms.Consumer.receiveQueue(Consumer.java:20) ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_121]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_121]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_121]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_121]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:196) ~[spring-messaging-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:113) ~[spring-messaging-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:104) ~[spring-jms-4.3.5.RELEASE.jar:4.3.5.RELEASE]
... 10 common frames omitted
我们发现,当消息失败时(抛异常,客户端没有ack),默认会重试6次,重试6次后,就会将失败的消息放到
DLQ队列中