activemq

ActiveMQ vs Apollo vs Kafka

▼魔方 西西 提交于 2019-12-03 01:10:07
问题 I don't have any previous experience with *MQs and I'm looking to build knowledge on JMS and message queues in general. That way, I wonder whether I should start with ActiveMQ or just "ignore" it altogether and start by teaching myself Apollo. Is Apollo as feature-complete as ActiveMQ? Does it implement JMS 2.0 (I see that ActiveMQ got stuck with 1.1)? Will I be missing something really important? Also, how does Kafka compare to these two solutions? 回答1: Apache ActiveMQ is a great workhorse

jersey rest web Service with Activemq middleware integration

匿名 (未验证) 提交于 2019-12-03 01:10:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: I have a Restful service API developed with JAX-RS and jersey. I have deployed the same in TOMCAT 7. Now I would like to implement Activemq so that I would keep all request in a queue and process the request resource. How to do this and integrate with tomcat7. How to integrate ActiveMq with Tomcat7 or my rest service webapp. How to call the service. Important :- Inside the Rest Api, I am using FilterChaining concept for security concern and after verification of the calling party, I am simply forwarding the request to the resource.

AMQPNETLITE - ActiveMQ Artemis (Red Hat AMQ) - autocreate multi-consumer multicast queue

匿名 (未验证) 提交于 2019-12-03 01:06:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: This qeuestion is on consuming the messages using AMQP in .Net. The documentation recommends amqpnetlite: https://access.redhat.com/documentation/en-us/red_hat_amq/7.0/html-single/using_the_amq_.net_client/index On subscribing to an address using AMQPNetLite, the address and the queue will be auto-created. The auto-created queue is always "unicast" though. I have not been able to auto-create a multicast queue that allowed any number of consumers. Code: private async Task RenewSession() { Connect = await Connection.Factory.CreateAsync(new

Spring JMS(ActiveMQ) delayed delivery of messages

匿名 (未验证) 提交于 2019-12-03 01:00:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: We're trying to set a delay on some JMS messages, so that a message will only be added to the queue/ received by the listener after x time. So far we've tried 2 approaches that didn't work. 1) According to the spring documentation, we can set the delivery delay on the JMSTemplate. This is the sample code we tried: @Autowired private JmsTemplate jmsTemplate; ... long deliveryDelay = ...; this.jmsTemplate.setDeliveryDelay(deliveryDelay); this.jmsTemplate.convertAndSend( queue.getName(), event); ... However, we get the following exception, even

WARNING as java.io.EOFException when ActiveMQ starts

匿名 (未验证) 提交于 2019-12-03 00:58:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: am trying to start the ActiveMQ 5.11 and I see a WARNING as below: WARN | Transport Connection to: tcp://127.0.0.1:40890 failed: java.io.EOFException My activemq.xml is as below: <transportConnectors> <transportConnector name="openwire" uri="tcp://0.0.0.0:${JMS_PORT}" /> <transportConnector name="stomp" uri="stomp://0.0.0.0:${JMS_STOMP_PORT}"/> <transportConnector name="ssl" uri="ssl://0.0.0.0:${JMS_SSL_PORT}"/> </transportConnectors> <sslContext> <sslContext keyStore="file:${JMS_KEY_STORE}" keyStorePassword="${JMS_KEY_STORE_PASSWORD}"

ActiveMQ embedded broker, exception in shutdown hook

匿名 (未验证) 提交于 2019-12-03 00:58:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I get the following error on shutdown, using an embedded broker: Exception in thread "ActiveMQ ShutdownHook" java.lang.NoClassDefFoundError: org/apache/activemq/broker/BrokerService Have I misconfigured something possibly? I used the config spelled out on the activemq page here: http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html (the configuration labeled "using spring-2.0" at the bottom). The messages are being delivered properly etc. so I'm not sure if this error is harmless. 回答1: This is an old issue that can

ActiveMQ Jolokia API How can I get the full Message Body

匿名 (未验证) 提交于 2019-12-03 00:56:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I want to write my own ActiveMQ Monitor. I can get Queues and Messages from a Queue. But the Message Body (content) is shorted. How can I get the full Message Body? This I have tested: Get: Always errors http://localhost:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=errors/browseMessages(java.lang.String)/JMSMessageID%3D%27ID%3AW530-62766-1419849619826-0%3A15%3A1%3A1%3A1%27 http://localhost:8161/api/jolokia/exec/org.apache.activemq:type=Broker,brokerName=localhost

ActiveMQ-CPP and Visual Studio 2003

自闭症网瘾萝莉.ら 提交于 2019-12-03 00:51:56
ActiveMQ CPP and Visual Studio 2003 I've have a requirement to get AMQ to work with some code that requires VS 7.1, however I'm having a difficult time getting it and various Apache libraries like apr etc to build using VS 7.1. There is a vs2008 solution/project for AMQ-CPP, I've used that as a template and tried to create one for VS 7.1, However when trying to build, I get errors like the following: "\amq\activemq-cpp-library-3.4.1\src\main\activemq\util\primitivemap.cpp(70): fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c', line 148

在一台服务器上启动多个Broker

匿名 (未验证) 提交于 2019-12-03 00:41:02
1:把整个conf文件夹复制一份,比如叫做conf2 2:修改里面的activemq.xml文件 (1)里面的brokerName 不能跟原来的重复 (2)数据存放的文件名称不能重复,比如: <kahaDB directory="${activemq.data}/kahadb_2"/> (3)所有涉及的transportConnectors 的端口,都要跟前面的不一样 3:修改jetty.xml,主要就是修改端口,比如: <property name=“port” value=“8181”/> 端口必须和前面的不一样 4:到bin下面,复制一个activemq,比如叫做activemq2: (1)修改程序的id,不能和前面的重复 ACTIVEMQ_PIDFILE="$ACTIVEMQ_DATA/activemq2-`hostname`.pid" (2)修改配置文件路径 ACTIVEMQ_CONF="$ACTIVEMQ_BASE/conf2" (3)修改端口,里面有个tcp的61616的端口,要改成不一样的,最好跟activemq.xml里面的tcp的端口一致 (4)然后就可以执行了,如果执行没有权限的话,就授权:chmod 751 activemq2 原文:https://www.cnblogs.com/xiaoliangup/p/9339527.html

关于windows下activeMQ的安装

匿名 (未验证) 提交于 2019-12-03 00:41:02
1.下载地址http://activemq.apache.org/activemq-5154-release.html 2.修改登录账号和密码,在配置文件jetty-realm.properties中。 3.修改端口,61616为对外服务端口号(在activemq.xml中修改),8161为控制器端口号(在jetty.xml中修改)。冲突时可根据情况进行配置。 4.默认不修改时,可访问http://localhost:8161/admin/index.jsp进行验证是否安装成功,登陆用户名,密码都为admin。可根据第二步修改配置。无异常时,显示结果如下: 原文:https://www.cnblogs.com/runn1ngCloud/p/9329353.html