Re: Virtual Topics without existing consumers

Messages sent to topics are kept until they have been delivered to all consumers, so messages sent to topics with no consumers are deleted immediately. Tim On Jun 22, 2017 10:06 AM, "sebasalvo" wrote: > Hi, > > I'm kind of a newbie in the ActiveMQ world. Please, let me ask you the > following:

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: No JMSDestination parameter specified

从官网新下的activemq,启动后浏览器访问，创建队列，一点create就报下面的错，不只是创建队列，创建topics也报这个错， org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: No JMSDestination parameter specified at org.springframework.web.servlet.FrameworkServle

Re: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: No JMSDestination parameter specified

才开始以为是版本的问题，下了三四个不同的版本，都报这个错 以前也从官网下过，没报这个错啊，静等大虾解救 -- View this message in context: http://activemq.2283324.n4.nabble.com/org-springframework-web-util-NestedServletException-Request-processing-failed-nested-exception-is-jad-tp4727806p4727807.html Sent from the ActiveMQ - User mailing list arch

Virtual Topics without existing consumers

Hi, I'm kind of a newbie in the ActiveMQ world. Please, let me ask you the following: What happens with messages delivered to a virtual topic that doesn't have a consumer (queues or regular topics) behind it? I mean, where do all those messages go? Are they kept in memory or in the kahadb storage

Re: Artemis v2.1 divert

Thanks Justin. flag was the reason for store filling up. We were thinking address itself is storing messages, but it was DLQ. Thanks for the help -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-v2-1-divert-tp4727498p4727759.html Sent from the ActiveMQ - User m

Re: Artemis 2.1.0 compatibility with 1.5.x

Thanks to your comment on the branch I've noticed I've posted the wrong branch, now I've fixed the branch name in the comment :P thanks! -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-1-0-compatibility-with-1-5-x-tp4727741p4727758.html Sent from the ActiveMQ -

Re: Message grouping and MQTT

That's what I was afraid of. Thank you! On Thu, Jun 22, 2017 at 7:46 AM, Timothy Bish wrote: > On 06/21/2017 08:51 PM, Stuart Small wrote: > >> I'm evaluating ActiveMQ for a new application I am building. Message >> grouping is the feature that has brought me to ActiveMQ and it looks >> perfec

Re: Message grouping and MQTT

On 06/21/2017 08:51 PM, Stuart Small wrote: I'm evaluating ActiveMQ for a new application I am building. Message grouping is the feature that has brought me to ActiveMQ and it looks perfect for what I want. The only problem is that I'm constrained to only using MQTT. It's unfortunately but sad

Re: CMS 3.9.2 process hangs when calling setMessageListener(..) in onMessage(...)

On 06/22/2017 04:48 AM, klaus.holst.jacobsen wrote: Hello! I would like to send a request and get a reply from a message handlers onMessage(...) method. Something like this: void MyClass::onMessage(cms::Message m) { cms::Destination* tempDest = session_->createTemporaryQueue(); cms::MessageCo

Re: High swap usage and network timeouts during heavy publishing

Have you confirmed (via techniques such as the ones described in https://www.cyberciti.biz/faq/linux-which-process-is-using-swap/) that the ActiveMQ process is the one whose pages are getting swapped? Also, what does top show your buffer usage (i.e. Linux using memory to buffer disk writes for per

Re: Artemis 2.1.0 compatibility with 1.5.x

A 1.5.1 client should be able to interact with a 2.1.0 broker. I don't know why there would be a difference in the size of the messages. To be clear, the new encoding applies to AMQP messages which you don't appear to be using. Can you work up a simple, reproducible test-case to demonstrate the

Re: Artemis 2.1.0 compatibility with 1.5.x

Hi, Yep, I'm testing what could be the cause right now. My fix is here: https://github.com/franz1981/activemq-artemis/tree/jms_core_q_already_exists_fix if you want to try it If the tests will be successfull I'll make a PR with it :) Regards, Franz -- View this message in context: http://acti

Artemis 2.1.0 compatibility with 1.5.x

We have been using Artemis 1.5.1. Recently we upgrade the server to 2.1.0. While it can communicate with 2.1.0 client successfully, it does not seem to work properly with 1.5.1 client. We are passing messages in protobuf format. The end result is the receiving end can no longer deserialize the pr

CMS 3.9.2 process hangs when calling setMessageListener(..) in onMessage(...)

Hello! I would like to send a request and get a reply from a message handlers onMessage(...) method. Something like this: void MyClass::onMessage(cms::Message m) { cms::Destination* tempDest = session_->createTemporaryQueue(); cms::MessageConsumer* responseConsumer = session_->createConsumer(te

Re: Switch to Artemis from ActiveMQ v5.14.4?

> protocol interoperability is available but still It looks like code changes are required from the client side. What code changes are required for OpenWire clients to connect to Artemis? Please be as specific as possible. > Will clients using ActiveMQ client jar be able to connect to the broker

Artemis as MQTT broker fail when load testing 10k publishers QoS1

Hello, I am currently using an artemis server as a mqtt broker for load testing, and it seems sending messages with QoS1 make it blow up pretty fast (10k connections publishing 1 message/s, usually break right at the end of the first 10k batch, my client receive 10k messages or less): I get a lot

Re: Switch to Artemis from ActiveMQ v5.14.4?

Regarding interoperability: As you mentioned protocol interoperability is available but still It looks like code changes are required from the client side. To be more specific : Will clients using ActiveMQ client jar be able to connect to the broker running with Artemis ? Eg: Currently clients