activemq | 易学教程

Spring JMS Activemq - set dead letter queue-name (DLQ)

阅读更多关于 Spring JMS Activemq - set dead letter queue-name (DLQ)

问题 We have 3 different projects that are running on the same ACTIVEMQ broker. Currently there is a single "DLQ" queue, we would like to set the dlq for each web application like so: dlq_webapp1 dlq_webapp2 dlq_webapp3 This way we will have more control on the retry flow. how can we configure it to be like so? here are some of our messaging beans: <bean id="redeliveryConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="${activemq_url}" />

How to set ActiveMQ port in Spring Boot?

阅读更多关于 How to set ActiveMQ port in Spring Boot?

问题 I have two Spring Boot applications running on one server. Both use embedded ActiveMQ JMS. I want to have separate JMS instance for each application. How could I set the port for each of them? Is there any property like spring.activemq.port ? When I run second application I get the following expected error: Failed to start JMX connector Cannot bind to URL [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi].

How to delay consuming messages in Apache Camel from ActiveMQ

阅读更多关于 How to delay consuming messages in Apache Camel from ActiveMQ

问题 I have a requirement where I need to throttle by shaping (queuing) inbound traffic when client app sends more than 1000 requests in a 5 sec time span. The solution I followed is: I have a camel:throttle setting max requests to 1000 and timespan to 5 sec. When threshold is exceeded I am catching throttle exception and within the onException block, I am sending the throttled messages to an ActiveMQ request queue for further processing later as Camel is overloaded based on 1000 req/ 5 sec config

ActiveMQ支持的传输协议

阅读更多关于 ActiveMQ支持的传输协议

连接到ActiveMQ 　Connector:ActiveMQ提供的，用来实现连接通信的功能。包括:client-to-broker、broker-to-broker。ActiveMQ允许客户端使用多种协议来进行连接。　　　　client-to-broker模式一般是配置文件中的transportConnector配置　　　　broker-to-broker:一般是指网络(network) ===后面学习 ActiveMQ支持的client-to-broker的通信协议如下: 最常用的也就是TCP和NIO 1.TCP：这个也是缺省值 2.NIO 3.UDP 4.SSL 5.Http(s) 6.VM：如果客户端和broker在一个虚拟机内的话，通过VM协议通讯在VM内通讯，从而减少网络传输的开销配置transportConnectors,位于conf/activemq.xml，大致如下:

ActiveMQ支持的传输协议

阅读更多关于 ActiveMQ支持的传输协议

------------------------------------------------------ ActiveMQ支持的client-broker通讯协议有：TCP、NIO、UDP、SSL、Http(s)、VM。其中配置Transport Connector的文件在activeMQ安装目录的conf/activemq.xml中的 <transportConnectors>标签之内。下面就具体来看看每一个通讯协议 (1)Transmission Control Protocol(TCP) 　　a.这是默认的Broker配置,TCP的Client监听端口61616 　　b.在网络传输数据前，必须要序列化数据，消息是通过一个叫wire protocol的来序列化成字节流。默认情况下，ActiveMQ把wire protocol叫做OpenWire,它的目的是促使网络上的效率和数据快速交互。　　c.TCP连接的URI形式如： tcp://hostname:port ?key=value&key=value, 后面的参数是可选　　d.TCP传输的优点：　　　　(d.1)TCP协议传输可靠性高，稳定性强　　　　(d.2)高效性：字节流方式传递，效率很高　　　　(d.3)有效性、可用性：应用广泛，支持任何平台　　e.关于Transport协议的可配置参数，可以参加官网

ActiveMQ支持的传输协议

阅读更多关于 ActiveMQ支持的传输协议

Connector：ActiveMQ提供的，用来实现连接通讯的功能。包括：client-tobroker、broker-to-broker。 ActiveMQ允许客户端使用多种协议来连接配置Transport Connector的文件在activeMQ安装目录的conf/activemq.xml中的<transportConnectors>标签之内。 <transportConnectors>  <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613

ActiveMQ传输协议

阅读更多关于 ActiveMQ传输协议

ActiveMQ默认的传输协议是TCP 　　在activemq的配置文件 /conf/activemq.xml可对配置文件进行修改和查看　　 tcp:openwire : 它是默认的　　tcp在网络传输前需要序列化数据，消息通过一个叫wire protocol的来序列化成字节流　　默认情况下ActiveMQ把wire protocol叫做OpenWire，目的是促使网络上的效率和数据快速交互　　　　tcp连接的URL：tcp://hostname:port?key=value&key=value，参数可选，如下　　　　　　　　配置为NIO,因为NIO的性能很好，所以一般都是用NIO <transportConnectors> <transportConnector name="nio" uri="nio://0.0.0.0:61616"/> </<transportConnectors> 　　官网配置地址：http://activemq.apache.org/configuring-transports 　如果不特别指定ActiveMQ的网络监听端口，这些端口都将使用BIO网络IO模型，如OpenWire,STOMP,AMQP等，　　所以为了为提高吞吐量，我们应该指明为nio 　　详细配置NIO：　　　　 1.配置文件加上NIO 　　

ActiveMQ 传输协议

阅读更多关于 ActiveMQ 传输协议

配置 ActiveMQ安装目录的 conf/activemq.xml 中的 <transportConnectors> 标签之内。配置示例 TCP（默认协议，性能相对可靠） Transmission Control Protocol(TCP) 这是默认的Broker配置,TCP的Client监听端口61616 在网络传输数据前，必须要序列化数据，消息是通过一个叫wire protocol的来序列化成字节流。默认情况下，ActiveMQ把wire protocol叫做OpenWire,它的目的是促使网络上的效率和数据快速交互。 TCP连接的URI形式如： tcp://localhost:port?key=value&key=value （后面的参数是可选） TCP传输的优点： TCP协议传输可靠性高，稳定性强高效性：字节流方式传递，效率很高有效性、可用性：应用广泛，支持任何平台 <transportConnectors> <transportConnector name="tcp" uri="tcp://localhost:61616?trace=true"/> </transportConnectors> NIO（基于TCP优化与扩展，扩展性高） New I/O API Protocol(NIO) NIO协议和TCP协议类似，但NIO更侧重于底层的访问操作

ActiveMQ - Removing queues programmatically

阅读更多关于 ActiveMQ - Removing queues programmatically

问题 Fellow StackOverflowers, is there a way for me to remove a queue or a topic in ActiveMQ programmatically? I am using ActiveMQ's standard persistency, and my application requires that, on startup, all new queues be dynamically re-created (unless there are messages stored in the queue, in which case, the queue should remain to exist). I am also creating all queues programmatically through sessions. Is there an equivalent to that procedure, only to delete a queue? Querying and iterating through

ActiveMQ Simple Authentication Plugin - user admin is not authorized to create: topic://ActiveMQ.Advisory.Connection

阅读更多关于 ActiveMQ Simple Authentication Plugin - user admin is not authorized to create: topic://ActiveMQ.Advisory.Connection

问题 I modified our ActiveMQ configuration to use ActiveMQ Simple Authentication Plugin with a single user and password that has all rights to the broker <plugins> <simpleAuthenticationPlugin> <users> <authenticationUser username="admin" password="pass" groups="admins,publishers,consumers" /> </users> </simpleAuthenticationPlugin> <authorizationPlugin> <map> <authorizationMap> <authorizationEntries> <authorizationEntry queue=">" write="producers" read="consumers" admin="admins" /> <

订阅 activemq