1.1 JMS简介
JMS的全称是Java Message Service,即Java消息服务。它主要用于在生产者和消费者之间进行消息传递,生产者负责产生消息,而消费者负责接收消息。把它应用到实际的业务需求中的话我们可以在特定的时候利用生产者生成一消息,并进行发送,对应的消费者在接收到对应的消息后去完成对应的业务逻辑。对于消息的传递有两种类型,一种是点对点的,即一个生产者和一个消费者一一对应;另一种是发布/订阅模式,即一个生产者产生消息并进行发送后,可以由多个消费者进行接收。
1.2 Spring整合JMS
对JMS做了一个简要介绍之后,接下来就讲一下Spring整合JMS的具体过程。JMS只是一个标准,真正在使用它的时候我们需要有它的具体实现,这里我们就使用Apache的activeMQ来作为它的实现。所使用的依赖利用Maven来进行管理,具体依赖如下:
- <dependencies>
- <dependency>
- <groupId>junit</groupId>
- <artifactId>junit</artifactId>
- <version>4.10</version>
- <scope>test</scope>
- </dependency>
- <dependency>
- <groupId>org.springframework</groupId>
- <artifactId>spring-context</artifactId>
- <version>${spring-version}</version>
- </dependency>
- <dependency>
- <groupId>org.springframework</groupId>
- <artifactId>spring-jms</artifactId>
- <version>${spring-version}</version>
- </dependency>
- <dependency>
- <groupId>org.springframework</groupId>
- <artifactId>spring-test</artifactId>
- <version>${spring-version}</version>
- </dependency>
- <dependency>
- <groupId>javax.annotation</groupId>
- <artifactId>jsr250-api</artifactId>
- <version>1.0</version>
- </dependency>
- <dependency>
- <groupId>org.apache.activemq</groupId>
- <artifactId>activemq-core</artifactId>
- <version>5.7.0</version>
- </dependency>
- </dependencies>
1.2.1 activeMQ准备
既然是使用的apache的activeMQ作为JMS的实现,那么首先我们应该到apache官网上下载activeMQ(http://activemq.apache.org/download.html),进行解压后运行其bin目录下面的activemq.bat文件启动activeMQ。
1.2.2配置ConnectionFactory
ConnectionFactory是用于产生到JMS服务器的链接的,Spring为我们提供了多个ConnectionFactory,有SingleConnectionFactory和CachingConnectionFactory。SingleConnectionFactory对于建立JMS服务器链接的请求会一直返回同一个链接,并且会忽略Connection的close方法调用。CachingConnectionFactory继承了SingleConnectionFactory,所以它拥有SingleConnectionFactory的所有功能,同时它还新增了缓存功能,它可以缓存Session、MessageProducer和MessageConsumer。这里我们使用SingleConnectionFactory来作为示例。
这样就定义好产生JMS服务器链接的ConnectionFactory了吗?答案是非也。Spring提供的ConnectionFactory只是Spring用于管理ConnectionFactory的,真正产生到JMS服务器链接的ConnectionFactory还得是由JMS服务厂商提供,并且需要把它注入到Spring提供的ConnectionFactory中。我们这里使用的是ActiveMQ实现的JMS,所以在我们这里真正的可以产生Connection的就应该是由ActiveMQ提供的ConnectionFactory。所以定义一个ConnectionFactory的完整代码应该如下所示:
- <!-- 真正可以产生Connection的ConnectionFactory,由对应的 JMS服务厂商提供-->
- <bean id="targetConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- </bean>
- <!-- Spring用于管理真正的ConnectionFactory的ConnectionFactory -->
- <bean id="connectionFactory" class="org.springframework.jms.connection.SingleConnectionFactory">
- <!-- 目标ConnectionFactory对应真实的可以产生JMS Connection的ConnectionFactory -->
- <property name="targetConnectionFactory" ref="targetConnectionFactory"/>
- </bean>
ActiveMQ为我们提供了一个PooledConnectionFactory,通过往里面注入一个ActiveMQConnectionFactory可以用来将Connection、Session和MessageProducer池化,这样可以大大的减少我们的资源消耗。当使用PooledConnectionFactory时,我们在定义一个ConnectionFactory时应该是如下定义:
- <!-- 真正可以产生Connection的ConnectionFactory,由对应的 JMS服务厂商提供-->
- <bean id="targetConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- </bean>
- <bean id="pooledConnectionFactory" class="org.apache.activemq.pool.PooledConnectionFactory">
- <property name="connectionFactory" ref="targetConnectionFactory"/>
- <property name="maxConnections" value="10"/>
- </bean>
- <bean id="connectionFactory" class="org.springframework.jms.connection.SingleConnectionFactory">
- <property name="targetConnectionFactory" ref="pooledConnectionFactory"/>
- </bean>
1.2.3配置生产者
配置好ConnectionFactory之后我们就需要配置生产者。生产者负责产生消息并发送到JMS服务器,这通常对应的是我们的一个业务逻辑服务实现类。但是我们的服务实现类是怎么进行消息的发送的呢?这通常是利用Spring为我们提供的JmsTemplate类来实现的,所以配置生产者其实最核心的就是配置进行消息发送的JmsTemplate。对于消息发送者而言,它在发送消息的时候要知道自己该往哪里发,为此,我们在定义JmsTemplate的时候需要往里面注入一个Spring提供的ConnectionFactory对象。
在真正利用JmsTemplate进行消息发送的时候,我们需要知道消息发送的目的地,即destination。在Jms中有一个用来表示目的地的Destination接口,它里面没有任何方法定义,只是用来做一个标识而已。当我们在使用JmsTemplate进行消息发送时没有指定destination的时候将使用默认的Destination。默认Destination可以通过在定义jmsTemplate bean对象时通过属性defaultDestination或defaultDestinationName来进行注入,defaultDestinationName对应的就是一个普通字符串。在ActiveMQ中实现了两种类型的Destination,一个是点对点的ActiveMQQueue,另一个就是支持订阅/发布模式的ActiveMQTopic。在定义这两种类型的Destination时我们都可以通过一个name属性来进行构造,如:
- <!--这个是队列目的地,点对点的-->
- <bean id="queueDestination" class="org.apache.activemq.command.ActiveMQQueue">
- <constructor-arg>
- <value>queue</value>
- </constructor-arg>
- </bean>
- <!--这个是主题目的地,一对多的-->
- <bean id="topicDestination" class="org.apache.activemq.command.ActiveMQTopic">
- <constructor-arg value="topic"/>
- </bean>
假设我们定义了一个ProducerService,里面有一个向Destination发送纯文本消息的方法sendMessage,那么我们的代码就大概是这个样子:
- package com.tiantian.springintejms.service.impl;
- import javax.annotation.Resource;
- import javax.jms.Destination;
- import javax.jms.JMSException;
- import javax.jms.Message;
- import javax.jms.Session;
- import org.springframework.jms.core.JmsTemplate;
- import org.springframework.jms.core.MessageCreator;
- import org.springframework.stereotype.Component;
- import com.tiantian.springintejms.service.ProducerService;
- @Component
- public class ProducerServiceImpl implements ProducerService {
- private JmsTemplate jmsTemplate;
- public void sendMessage(Destination destination, final String message) {
- System.out.println("---------------生产者发送消息-----------------");
- System.out.println("---------------生产者发了一个消息:" + message);
- jmsTemplate.send(destination, new MessageCreator() {
- public Message createMessage(Session session) throws JMSException {
- return session.createTextMessage(message);
- }
- });
- }
- public JmsTemplate getJmsTemplate() {
- returnjmsTemplate;
- }
- @Resource
- public void setJmsTemplate(JmsTemplate jmsTemplate) {
- this.jmsTemplate = jmsTemplate;
- }
- }
我们可以看到在sendMessage方法体里面我们是通过jmsTemplate来发送消息到对应的Destination的。到此,我们生成一个简单的文本消息并把它发送到指定目的地Destination的生产者就配置好了。
1.2.4配置消费者
生产者往指定目的地Destination发送消息后,接下来就是消费者对指定目的地的消息进行消费了。那么消费者是如何知道有生产者发送消息到指定目的地Destination了呢?这是通过Spring为我们封装的消息监听容器MessageListenerContainer实现的,它负责接收信息,并把接收到的信息分发给真正的MessageListener进行处理。每个消费者对应每个目的地都需要有对应的MessageListenerContainer。对于消息监听容器而言,除了要知道监听哪个目的地之外,还需要知道到哪里去监听,也就是说它还需要知道去监听哪个JMS服务器,这是通过在配置MessageConnectionFactory的时候往里面注入一个ConnectionFactory来实现的。所以我们在配置一个MessageListenerContainer的时候有三个属性必须指定,一个是表示从哪里监听的ConnectionFactory;一个是表示监听什么的Destination;一个是接收到消息以后进行消息处理的MessageListener。Spring一共为我们提供了两种类型的MessageListenerContainer,SimpleMessageListenerContainer和DefaultMessageListenerContainer。
SimpleMessageListenerContainer会在一开始的时候就创建一个会话session和消费者Consumer,并且会使用标准的JMS MessageConsumer.setMessageListener()方法注册监听器让JMS提供者调用监听器的回调函数。它不会动态的适应运行时需要和参与外部的事务管理。兼容性方面,它非常接近于独立的JMS规范,但一般不兼容Java EE的JMS限制。
大多数情况下我们还是使用的DefaultMessageListenerContainer,跟SimpleMessageListenerContainer相比,DefaultMessageListenerContainer会动态的适应运行时需要,并且能够参与外部的事务管理。它很好的平衡了对JMS提供者要求低、先进功能如事务参与和兼容Java EE环境。
定义处理消息的MessageListener
要定义处理消息的MessageListener我们只需要实现JMS规范中的MessageListener接口就可以了。MessageListener接口中只有一个方法onMessage方法,当接收到消息的时候会自动调用该方法。
- package com.tiantian.springintejms.listener;
- import javax.jms.JMSException;
- import javax.jms.Message;
- import javax.jms.MessageListener;
- import javax.jms.TextMessage;
- public class ConsumerMessageListener implements MessageListener {
- public void onMessage(Message message) {
- //这里我们知道生产者发送的就是一个纯文本消息,所以这里可以直接进行强制转换
- TextMessage textMsg = (TextMessage) message;
- System.out.println("接收到一个纯文本消息。");
- try {
- System.out.println("消息内容是:" + textMsg.getText());
- } catch (JMSException e) {
- e.printStackTrace();
- }
- }
- }
有了MessageListener之后我们就可以在Spring的配置文件中配置一个消息监听容器了。
- <!--这个是队列目的地-->
- <bean id="queueDestination" class="org.apache.activemq.command.ActiveMQQueue">
- <constructor-arg>
- <value>queue</value>
- </constructor-arg>
- </bean>
- <!-- 消息监听器 -->
- <bean id="consumerMessageListener" class="com.tiantian.springintejms.listener.ConsumerMessageListener"/>
- <!-- 消息监听容器 -->
- <bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
- <property name="connectionFactory" ref="connectionFactory" />
- <property name="destination" ref="queueDestination" />
- <property name="messageListener" ref="consumerMessageListener" />
- </bean>
我们可以看到我们定义了一个名叫queue的ActiveMQQueue目的地,我们的监听器就是监听了发送到这个目的地的消息。
至此我们的生成者和消费者都配置完成了,这也就意味着我们的整合已经完成了。这个时候完整的Spring的配置文件应该是这样的:
- <?xml version="1.0" encoding="UTF-8"?>
- <beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
- xmlns:jms="http://www.springframework.org/schema/jms"
- xsi:schemaLocation="http://www.springframework.org/schema/beans
- http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
- http://www.springframework.org/schema/context
- http://www.springframework.org/schema/context/spring-context-3.0.xsd
- http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
- http://www.springframework.org/schema/jms http://www.springframework.org/schema/jms/spring-jms-3.0.xsd">
- <context:component-scan base-package="com.tiantian" />
- <!-- Spring提供的JMS工具类,它可以进行消息发送、接收等 -->
- <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <!-- 这个connectionFactory对应的是我们定义的Spring提供的那个ConnectionFactory对象 -->
- <property name="connectionFactory" ref="connectionFactory"/>
- </bean>
- <!-- 真正可以产生Connection的ConnectionFactory,由对应的 JMS服务厂商提供-->
- <bean id="targetConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- </bean>
- <!-- Spring用于管理真正的ConnectionFactory的ConnectionFactory -->
- <bean id="connectionFactory" class="org.springframework.jms.connection.SingleConnectionFactory">
- <!-- 目标ConnectionFactory对应真实的可以产生JMS Connection的ConnectionFactory -->
- <property name="targetConnectionFactory" ref="targetConnectionFactory"/>
- </bean>
- <!--这个是队列目的地-->
- <bean id="queueDestination" class="org.apache.activemq.command.ActiveMQQueue">
- <constructor-arg>
- <value>queue</value>
- </constructor-arg>
- </bean>
- <!-- 消息监听器 -->
- <bean id="consumerMessageListener" class="com.tiantian.springintejms.listener.ConsumerMessageListener"/>
- <!-- 消息监听容器 -->
- <bean id="jmsContainer"
- class="org.springframework.jms.listener.DefaultMessageListenerContainer">
- <property name="connectionFactory" ref="connectionFactory" />
- <property name="destination" ref="queueDestination" />
- <property name="messageListener" ref="consumerMessageListener" />
- </bean>
- </beans>
接着我们来测试一下,看看我们的整合是否真的成功了,测试代码如下:
- package com.tiantian.springintejms.test;
- import javax.jms.Destination;
- import org.junit.Test;
- import org.junit.runner.RunWith;
- import org.springframework.beans.factory.annotation.Autowired;
- import org.springframework.beans.factory.annotation.Qualifier;
- import org.springframework.test.context.ContextConfiguration;
- import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
- import com.tiantian.springintejms.service.ProducerService;
- @RunWith(SpringJUnit4ClassRunner.class)
- @ContextConfiguration("/applicationContext.xml")
- public class ProducerConsumerTest {
- @Autowired
- private ProducerService producerService;
- @Autowired
- @Qualifier("queueDestination")
- private Destination destination;
- @Test
- public void testSend() {
- for (int i=0; i<2; i++) {
- producerService.sendMessage(destination, "你好,生产者!这是消息:" + (i+1));
- }
- }
- }
在上面的测试代码中我们利用生产者发送了两个消息,正常来说,消费者应该可以接收到这两个消息。运行测试代码后控制台输出如下:
看,控制台已经进行了正确的输出,这说明我们的整合确实是已经成功了。
附:
- SpringInteJMS_项目源码_.zip (70.2 KB)
- 下载次数: 1194
顶
踩
评论
按照上述配置完毕之后,
提示org.springframework.jms.core.JmsTemplate没有指定defaultDestinationName,于是把queueDestition给它指定.
指定完毕之后,可以发送消息,但是接收不到消息.
我的spring版本3.2.9.
从网上百度了下,说是消息监听容器需要添加
<property name="pubSubDomain" value="false"/>
<property name="pubSubNoLocal" value="false"/>
但是仍然接收不到信息...
请教下,这个是什么问题 ?? 非常感谢!!!
发送者是 一个main入口的程序
接收者是 一个web
代码运行正常
但是 一旦activeMQ 重启,就不正常了!不重启就接收不到信息
我想应该是connection 的问题,但是不晓得怎么处理
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
我回头研究一下。
请问你的这个异常是在什么情况下出现的呢?我这里测试一直没有出现这个问题。
我之前在weblogic上运行是没有这个问题的,单独使用junit进行测试时出现了该问题,这就是一个警告信息“ WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove ses
sion from connection that had not been registered”,对系统不会有影响。从提示信息来看,说的是不能从connection移除一个没有注册过的session,那就很好理解了,在单元测试运行时建立有对应的connection和session,运行完之后当前应用就执行完了,connection也关闭了,但是这个时候原先的session没有关闭,导致第二次运行时在新建立的connection中尝试移除之前的session失败,出现上述异步错误。这个问题在web环境下貌似是不会出现的。(至少我使用weblogic时没有出现)
我用的是apache-activemq-5.8.0
这个跟版本应该没有什么关系,根据activeMQ官方的说法,在进行单元测试的时候比较容易出现各种各样的问题,估计上述问题就是其中之一。找到一个解决办法就是把ActiveMQConnectionFactory再用PooledConnectionFactory封装一下,进行池化处理。代码如下:
- <bean id="targetConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- </bean>
- <bean id="pooledConnectionFactory" class="org.apache.activemq.pool.PooledConnectionFactory">
- <property name="connectionFactory" ref="targetConnectionFactory"/>
- <property name="maxConnections" value="10"/>
- </bean>
- <bean id="connectionFactory" class="org.springframework.jms.connection.SingleConnectionFactory">
- <property name="targetConnectionFactory" ref="pooledConnectionFactory"/>
- </bean>
这样在操作多次之后ActiveMQ就不会再抛不能移除session之类的警告异常信息了。使用上述代码改造之后ActiveMQ控制台会输出 INFO | Transport failed: java.net.SocketException: Connection reset这样的信息,这个对于消息的发送和接收也是没有影响的。
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
我回头研究一下。
请问你的这个异常是在什么情况下出现的呢?我这里测试一直没有出现这个问题。
我之前在weblogic上运行是没有这个问题的,单独使用junit进行测试时出现了该问题,这就是一个警告信息“ WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove ses
sion from connection that had not been registered”,对系统不会有影响。从提示信息来看,说的是不能从connection移除一个没有注册过的session,那就很好理解了,在单元测试运行时建立有对应的connection和session,运行完之后当前应用就执行完了,connection也关闭了,但是这个时候原先的session没有关闭,导致第二次运行时在新建立的connection中尝试移除之前的session失败,出现上述异步错误。这个问题在web环境下貌似是不会出现的。(至少我使用weblogic时没有出现)
我用的是apache-activemq-5.8.0
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
我回头研究一下。
请问你的这个异常是在什么情况下出现的呢?我这里测试一直没有出现这个问题。
我之前在weblogic上运行是没有这个问题的,单独使用junit进行测试时出现了该问题,这就是一个警告信息“ WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove ses
sion from connection that had not been registered”,对系统不会有影响。从提示信息来看,说的是不能从connection移除一个没有注册过的session,那就很好理解了,在单元测试运行时建立有对应的connection和session,运行完之后当前应用就执行完了,connection也关闭了,但是这个时候原先的session没有关闭,导致第二次运行时在新建立的connection中尝试移除之前的session失败,出现上述异步错误。这个问题在web环境下貌似是不会出现的。(至少我使用weblogic时没有出现)
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
我回头研究一下。
请问你的这个异常是在什么情况下出现的呢?我这里测试一直没有出现这个问题。
JMS就是生产者与消费者模式。消费者负责消费生产者产生的消息。通过JMS可以做后台的异步操作,应用到具体工作中的话,有用它来发内部消息的、发邮件的、发短信的,做大操作时在后台做异步操作的。
跟task 有什么区别
你的task一般是定时任务,而这个JMS是在有需要的时候由人工发送消息;另外我们发送的消息可以当做参数,消费者接收到消息之后可以根据消息内容的不同做不同的事情。
JMS就是生产者与消费者模式。消费者负责消费生产者产生的消息。通过JMS可以做后台的异步操作,应用到具体工作中的话,有用它来发内部消息的、发邮件的、发短信的,做大操作时在后台做异步操作的。
跟task 有什么区别
JMS就是生产者与消费者模式。消费者负责消费生产者产生的消息。通过JMS可以做后台的异步操作,应用到具体工作中的话,有用它来发内部消息的、发邮件的、发短信的,做大操作时在后台做异步操作的。
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
我回头研究一下。
java.lang.IllegalStateException: Cannot remove session from connection that had not been registered: ID:user-PC-61504-13
72256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:678)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:74)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not b
een registered: ID:user-PC-61504-1372256221562-1:1
java.lang.IllegalStateException: Cannot remove a consumer from a connection that had not been registered: ID:user-PC-615
04-1372256221562-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:637)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:329)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:184)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:288)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:722)
WARN | Transport Connection to: tcp://127.0.0.1:61505 failed: java.net.SocketException: Software caused connection abor
t: recv failed
如果是在接收过程中的消息丢失的话,那属于整合后事务控制的范围,这个在以后会讲到。如果是发送时候的消息丢失的话,那就属于对JMS的讨论了,不在本文讨论范围之内。 http://www.myexception.cn/software-architecture-design/899510.html这篇文章有讨论,希望对你有帮助。