activemq

How to simulate message redelivery in AUTO_ACKNOWLEDGE JMS Session Scenario?

大城市里の小女人 提交于 2019-12-03 07:52:15
In the following test I'm trying to simulate the following scenario: A message queue is started. A consumer designed to fail during message processing is started. A message is produced. The consumer starts processing the message. During processing an exception is thrown to simulate message processing failure. The failing consumer is stopped. Another consumer is started with the intent to pick up the redelivered message. But my test fails and the message is not redelivered to the new consumer. I'll appreciate any hints on this. MessageProcessingFailureAndReprocessingTest.java

How to configure embedded ActiveMQ Broker URL with Spring Boot

匿名 (未验证) 提交于 2019-12-03 07:36:14
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I followed a simple example of setting up and running embedded ActiveMQ with Spring Boot (version 1.4.X). Here's link to the example https://spring.io/guides/gs/messaging-jms/ My class is structured as below: @SpringBootApplication @EnableJms public class Application { @Autowired ConfigurableApplicationContext context; @Bean JmsListenerContainerFactory<?> myJmsContainerFactory(ConnectionFactory connectionFactory) { SimpleJmsListenerContainerFactory factory = new SimpleJmsListenerContainerFactory(); factory.setConnectionFactory

Max MQTT connections

◇◆丶佛笑我妖孽 提交于 2019-12-03 07:23:05
I have a need to create a server farm that can handle 5+ million connections, 5+ million topics (one per client), process 300k messages/sec. I tried to see what various message brokers were capable so I am currently using two RHEL EC2 instances (r3.4xlarge) to make lots of available resources. So you do not need to look it up, it has 16vCPU, 122GB RAM. I am nowhere near that limit in usage. I am unable to pass the 600k connections limit. Since there doesn't seem to be any O/S limitation (plenty of RAM/CPU/etc.) on either the client nor the server what is limiting me? I have edited /etc

javax.jms.JMSException: Failed to build body from content. Serializable class not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden class com.javaliao.portal.model.TbLogVisit! T

北城余情 提交于 2019-12-03 06:59:51
javax.jms.jmsexception:无法从内容生成正文。 可序列化类不可用于代理 原因:java.lang.ClassNotFoundException: 禁止类com.javaliao.portal.model.TbLogVisit不信任将此类序列化为objectMessage负载。 有关如何配置受信任类的详细信息,请查看http://activemq.apache.org/objectmessage.html。 控制台打印:javax.jms.JMSException: Failed to build body from content. Serializable class not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden class com.javaliao.portal.model.TbLogVisit! This class is not trusted to be serialized as ObjectMessage payload. Please take a look at http://activemq.apache.org/objectmessage.html for more information on how to configure

Difference between Pending Messages and Enqueue Counter in Active MQ?

六月ゝ 毕业季﹏ 提交于 2019-12-03 06:50:18
问题 In the Active MQ Admin console of what is the difference between "Number Of Pending Messages" and "Messages Enqueued"? When a Message is placed on to the queue, should both these values should match? 回答1: pending messages = number of messages CURRENTLY waiting for delivery in the destination (the current size of the queue) enqueued messages = number of messages that where enqueued in the destination since the last statistic reset. This number can only rise. dequeued messages = messages

Linux下安装 Apollo

╄→гoц情女王★ 提交于 2019-12-03 06:49:07
Apollo以ActiveMQ原型为基础,是一个更快、更可靠、更易于维护的消息代理工具。Apache称Apollo为最快、最强健的STOMP(Streaming Text Orientated Message Protocol,流文本定向消息协议)服务器. 它采用一个完全不同的消息分发架构,同ActiveMQ一样支持多种协议。如STOMP,AMQP,MQTT,Openwire,SSL和WebSockets. 一:linux下Apollo的安装 下载 apache-apollo-1.7-unix-distro.tar.gz 文件放到/usr/local/src目录下面 加压缩文件 tar -zxvf apache-apollo-1.7-unix-distro.tar.gz -C /usr/local 二:创建broker实例 一个broker实例是一个文件夹,其中包含所有的配置文件及运行时的数据,不如日志和消息数据。Apollo强烈建议不要把实例同安装文件放在一起。 在linux操作系统下面,建议将实例建在/var/lib/目录下面 cd /var/lib /usr/local/apache-apollo-1.7/bin/apollo create mybroker 创建成功后,在/var/lib/mybroker目录下可以看到如下目录 bin--------------------

Active MQ vs JBoss Messaging

南楼画角 提交于 2019-12-03 05:46:56
问题 I am going to choose a JMS message broker for a project. It is critical that the JMS server is stable and can handle a high load of messages. I have narrowed down the list to include Active MQ and JBoss Messaging. I was wondering if any of you have any experience with any of these or even better have tried both of them in the same environment. Any link to a research paper or similar would be nice. 回答1: JBoss Messaging is now in bug fix mode only, since JBoss / Red Hat has a new Java messaging

How to send ERROR message to STOMP clients with Spring WebSocket?

孤者浪人 提交于 2019-12-03 05:44:42
I am using Spring's STOMP over WebSocket implementation with a full-featured ActiveMQ broker. When users SUBSCRIBE to a topic, there is some permissions logic that they must pass through before being successfully subscribed. I am using a ChannelInterceptor to apply the permissions logic, as configured below: WebSocketConfig.java: @EnableWebSocketMessageBroker public class WebSocketConfig extends AbstractWebSocketMessageBrokerConfigurer { @Override public void registerStompEndpoints(StompEndpointRegistry registry) { registry.addEndpoint("/stomp") .setAllowedOrigins("*") .withSockJS(); }

jms producer performance with spring

空扰寡人 提交于 2019-12-03 04:52:29
问题 i created a simple producer consumer simulation based on spring, jms and activemq, i'm trying to reach high performance from both sides, producers and consumers, Connection settings : <tx:annotation-driven /> <bean id="transactionManager" class="org.springframework.jms.connection.JmsTransactionManager"> <property name="connectionFactory" ref="connectionFactory" /> </bean> <amq:connectionFactory id="amqConnectionFactory" brokerURL="failover:(tcp://${broker.url}:61616)" /> <bean id=

activemq 配置持久化文件

纵然是瞬间 提交于 2019-12-03 04:24:50
activemq.xml: ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------start <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the