ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory( "tcp://10.10.10.101:61616"); Connection connection = factory.createConnection(); connection.start(); final FileWriter fw=new FileWriter("log_.txt",true); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); Topic topic = session.createTopic("receive"); MessageConsumer consumer1 = session.createConsumer(topic); consumer1.receive(600000); consumer1.setMessageListener(new MessageListener() { public void onMessage(Message message) { System.out.println("收到一条消息: 开始收听消息"); TextMessage tm = (TextMessage) message; try { fw.append(tm.getText()+"\r\n"); System.out.println(tm.getText()); fw.flush(); //System.out.println("Received message: " + tm.getText()); } catch (JMSException e) { e.printStackTrace(); } catch (IOException e) { // TODO 自动生成的 catch 块 e.printStackTrace(); } } }); /*session.close(); connection.stop(); connection.close();*/ }
哪位高手给看下,这个是接受消息的,运行一天两天后就无法接受到消息了。
日志文件:
2014-06-23 09:35:55 [ ActiveMQ InactivityMonitor WriteCheckTimer:253832111 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:35:55 [ ActiveMQ InactivityMonitor Worker:253832112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:05 [ ActiveMQ InactivityMonitor WriteCheckTimer:253842111 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:36:05 [ ActiveMQ InactivityMonitor Worker:253842112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:15 [ ActiveMQ InactivityMonitor WriteCheckTimer:253852112 ] - [ DEBUG ] WriteChecker: 10001ms elapsed since last write check. 2014-06-23 09:36:15 [ ActiveMQ InactivityMonitor Worker:253852112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:22 [ ActiveMQ InactivityMonitor ReadCheckTimer:253858742 ] - [ DEBUG ] 30000ms elapsed since last read check. 2014-06-23 09:36:25 [ ActiveMQ InactivityMonitor WriteCheckTimer:253862111 ] - [ DEBUG ] WriteChecker: 9999ms elapsed since last write check. 2014-06-23 09:36:25 [ ActiveMQ InactivityMonitor Worker:253862112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:35 [ ActiveMQ InactivityMonitor WriteCheckTimer:253872111 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:36:35 [ ActiveMQ InactivityMonitor Worker:253872112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:45 [ ActiveMQ InactivityMonitor WriteCheckTimer:253882112 ] - [ DEBUG ] WriteChecker: 10001ms elapsed since last write check. 2014-06-23 09:36:45 [ ActiveMQ InactivityMonitor Worker:253882113 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:36:52 [ ActiveMQ InactivityMonitor ReadCheckTimer:253888743 ] - [ DEBUG ] 30000ms elapsed since last read check. 2014-06-23 09:36:55 [ ActiveMQ InactivityMonitor WriteCheckTimer:253892113 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:36:55 [ ActiveMQ InactivityMonitor Worker:253892113 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:05 [ ActiveMQ InactivityMonitor WriteCheckTimer:253902112 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:05 [ ActiveMQ InactivityMonitor Worker:253902113 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:15 [ ActiveMQ InactivityMonitor WriteCheckTimer:253912112 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:15 [ ActiveMQ InactivityMonitor Worker:253912112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:22 [ ActiveMQ InactivityMonitor ReadCheckTimer:253918742 ] - [ DEBUG ] 30000ms elapsed since last read check. 2014-06-23 09:37:25 [ ActiveMQ InactivityMonitor WriteCheckTimer:253922112 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:25 [ ActiveMQ InactivityMonitor Worker:253922114 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:35 [ ActiveMQ InactivityMonitor WriteCheckTimer:253932113 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:35 [ ActiveMQ InactivityMonitor Worker:253932113 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:45 [ ActiveMQ InactivityMonitor WriteCheckTimer:253942112 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:45 [ ActiveMQ InactivityMonitor Worker:253942113 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616] 2014-06-23 09:37:52 [ ActiveMQ InactivityMonitor ReadCheckTimer:253948742 ] - [ DEBUG ] 30000ms elapsed since last read check. 2014-06-23 09:37:55 [ ActiveMQ InactivityMonitor WriteCheckTimer:253952112 ] - [ DEBUG ] WriteChecker: 10000ms elapsed since last write check. 2014-06-23 09:37:55 [ ActiveMQ InactivityMonitor Worker:253952112 ] - [ DEBUG ] Running WriteCheck[tcp://127.0.0.1:61616]
相关推荐
activeMQ的测试工具,用于发送和接收activeMQ消息,jar包形式的,安装完jdk之后用java -jar xxx.jar命令运行
整合Spring + ActiveMQ 的朋友可以下载看一下 简单易懂
springboot集成activemq实现消息接收demo
activemq 通过ajax发送接收消息简单例子
SpringBoot+ActiveMq+MQTT实现消息的发送和接收 后台消费者、生产者、消息发送接口、发送消息业务类等相关配置
activeMQ的发送消息后接收者返回信息
本代码关于activemq-cpp的核心代码参考的chenxun2009的博客园,其他部分包括:从配置文件中读取消息通道,过滤条件等信息。
简单的activemq点对点的同步消息模型
这是我精力整理的ActiveMQ发送和接收protobuf协议消息的实例。 也对ActiveMQ进行了简化封装,也配置了自动重连机制,亲测可用!
PHP过滤(selector)接收ActiveMQ的指定队列或者主题消息
springboot整合 activeMq 消费者 消费接收消息 包含队列模式点对点发 以及 主题模式一对多 这是消费者的demo consumer 。 里面有消息重发机制,手动确认ACK模式。 配合 producer 生产者demo使用。
springboot整合ActiveMQ源码,适合范围消息队列入门小伙伴,对ActiveMQ消息队列不太了解,不知道如何发送消息,接收消息可以围观。
ActiveMQ(包括消息生成端和andorid消息接受端),实现了点对点的消息推送,和广播消息推送,当然离线推送也实现了。
详细描述了ActiveMQ消息过期-时间设置和自动清除解决方案。
用C#实现的ActiveMQ发布/订阅消息传送源程序
activemq与spring整合发送jms消息入门实例 jar 包和实例代码都在压缩包里了
百度spring整合activemq 发现几乎都只是在xml文件配置固定的消息队列而且太麻烦。并没有根据需求进行动态生成主题和队列。本文档参考了纯粹的activemq java代码和百度上的demo,很简洁的实现了动态消息队列的生成和...
ActiveMQ队列消息过期时间设置和自动清除解决方案.docx
一个用Spring+Activemq实现的消息平台