activemq用message确认消息的问题

最新推荐文章于 2021-07-29 21:58:29 发布

yixueweima

最新推荐文章于 2021-07-29 21:58:29 发布

阅读量1.4k

点赞数

CC 4.0 BY-SA版权

分类专栏： ActiveMQ

本文链接：https://blog.youkuaiyun.com/yixueweima/article/details/86516974

ActiveMQ 专栏收录该内容

2 篇文章

订阅专栏

探讨Spring框架中JMS消息监听器的三种确认模式：auto、client和trans。auto模式下，消息在到达监听器前即被确认，异常不触发重发；client和trans模式则在监听器执行后确认，异常时触发重发。深入解析源码，展示如何通过回滚和恢复机制实现消息重发。

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

首先，用auto模式，在onmessage之前就已经确认消息了。这时候如果onmessage中报错了，消息也不会重发。这是org.springframework.jms.listener.DefaultMessageListenerContainer类源码中的注释片段：“AUTO_ACKNOWLEDGE" mode, this container applies automatic message acknowledgment before listener execution, with no redelivery in case of an exception。大概意思就是我说的auto模式，容器自动在执行listener之前就自动确认消息了，遇到异常也不会重发了。

如果是client或者是trans模式，这个在执行完后会确认，如果报错，消息就不会被确认，会触发重发机制。org.springframework.jms.listener.AbstractMessageListenerContainer类中部分代码，可以看到消息被确认。

	/**
	 * Execute the specified listener,
	 * committing or rolling back the transaction afterwards (if necessary).
	 * @param session the JMS Session to operate on
	 * @param message the received JMS Message
	 * @throws JMSException if thrown by JMS API methods
	 * @see #invokeListener
	 * @see #commitIfNecessary
	 * @see #rollbackOnExceptionIfNecessary
	 * @see #convertJmsAccessException
	 */
	protected void doExecuteListener(Session session, Message message) throws JMSException {
		if (!isAcceptMessagesWhileStopping() && !isRunning()) {
			if (logger.isWarnEnabled()) {
				logger.warn("Rejecting received message because of the listener container " +
						"having been stopped in the meantime: " + message);
			}
			rollbackIfNecessary(session);
			throw new MessageRejectedWhileStoppingException();
		}

		try {
			invokeListener(session, message);
		}
		catch (JMSException ex) {
			rollbackOnExceptionIfNecessary(session, ex);
			throw ex;
		}
		catch (RuntimeException ex) {
			rollbackOnExceptionIfNecessary(session, ex);
			throw ex;
		}
		catch (Error err) {
			rollbackOnExceptionIfNecessary(session, err);
			throw err;
		}
		commitIfNecessary(session, message);
	}

	/**
	 * Perform a commit or message acknowledgement, as appropriate.
	 * @param session the JMS Session to commit
	 * @param message the Message to acknowledge
	 * @throws javax.jms.JMSException in case of commit failure
	 */
	protected void commitIfNecessary(Session session, Message message) throws JMSException {
		// Commit session or acknowledge message.
		if (session.getTransacted()) {
			// Commit necessary - but avoid commit call within a JTA transaction.
			if (isSessionLocallyTransacted(session)) {
				// Transacted session created by this container -> commit.
				JmsUtils.commitIfNecessary(session);
			}
		}
		else if (message != null && isClientAcknowledge(session)) {
			message.acknowledge();
		}
	}

这里的重发机制就是这个方法，主要是rollback和recover方法

	/**
	 * Perform a rollback, handling rollback exceptions properly.
	 * @param session the JMS Session to rollback
	 * @param ex the thrown application exception or error
	 * @throws javax.jms.JMSException in case of a rollback error
	 */
	protected void rollbackOnExceptionIfNecessary(Session session, Throwable ex) throws JMSException {
		try {
			if (session.getTransacted()) {
				if (isSessionLocallyTransacted(session)) {
					// Transacted session created by this container -> rollback.
					if (logger.isDebugEnabled()) {
						logger.debug("Initiating transaction rollback on application exception", ex);
					}
					JmsUtils.rollbackIfNecessary(session);
				}
			}
			else if (isClientAcknowledge(session)) {
				session.recover();
			}
		}
		catch (IllegalStateException ex2) {
			logger.debug("Could not roll back because Session already closed", ex2);
		}
		catch (JMSException ex2) {
			logger.error("Application exception overridden by rollback exception", ex);
			throw ex2;
		}
		catch (RuntimeException ex2) {
			logger.error("Application exception overridden by rollback exception", ex);
			throw ex2;
		}
		catch (Error err) {
			logger.error("Application exception overridden by rollback error", ex);
			throw err;
		}
	}