Re: How to cleanly close embedded ActiveMQ Artemis

I loaded JavaLite into my IDE and reproduced some test failures. Here are my observations... One thing that I noticed is that it's possible for some of your tests to leak brokers. Any test that has an assertion before the broker is stopped can leak if that assertion fails because the test will ter

Re: durable subscribers in artemis cluster

Thanks for the input and clarification, Justin! I found a misconfiguration of the property redistribution-delay in the cluster, that's why it did not behave the way I expected. Now it behaves as expected, and as you explained. Regarding the reason why we are implementing a cluster: We are not

Re: Connecting to ActiveMQ (classic) server with a browser

For what it's worth, you can find some documentation on OpenWire here [1]. That doc is a bit out-dated but most of it is still relevant. It looks like the best documentation on this subject. The data that your browser received is part of the WIREFORMAT_INFO which is part of the connection negotiati

Re: Connecting to ActiveMQ (classic) server with a browser

All those details are part of OpenWire's wire format. I'm not 100% sure why your browser is getting that response, but any OpenWire client would get the same information. My guess is that is part of the OpenWire connection negotiation. After the broker sees that no connection negotiation happens f

Re: durable subscribers in artemis cluster

> Justin, is the documentation wrong for the boolean values for the legacy forward-when-no-consumers attribute that it associates with STRICT and ON_DEMAND? It seems like STRICT should be false and ON_DEMAND should be true. No, the documentation is accurate. When using STRICT then nodes will forwa

POD restarting for HA ActiveMQ Deployment in Kubernetes

I have deployed two statefulset replicas of ActiveMQ 5.15.13 as Network Broker, but second POD activemq-1 is restarting after every 4m51s (I removed readiness and liveness probes too), I enabled debug logs but could not find any clue **ActiveMQ-0:** http://activemq.apache.org/schema/core";

Connecting to ActiveMQ (classic) server with a browser

There's something seemingly weird going on when connecting with a browser to the ssl-secured Openwire port of an ActiveMQ (classic) server. Using this Url: https://AMQ-HOST:OPENWIRE-PORT The browser sends off a GET request and after 30 seconds actually receives a response from ActiveMQ. The pa

Re: durable subscribers in artemis cluster

> If the consumer is disconnected, and queues exists on all nodes, the incoming messages will be round-robined among the nodes. And this means that the consumer must connect to all nodes in the cluster to retrieve all messages that have been published meanwhile it was disconnected. Given that you'

Re: Need spring upgrade in ActiveMQ

I agree: my point is that Spring 4.3.29 fixes all open CVE up to know. Now, I’m working on Spring 5.x upgrade. So, just wait a bit and we will have it very soon (it’s almost done, just have to polish some changes ;)). Regards JB > Le 2 déc. 2020 à 15:35, ragul rangarajan a écrit : > > Thank

Re: Need spring upgrade in ActiveMQ

Thanks for the update JB. But my concern for the need for Spring 5 Upgrade is more on that* Spring 4.3.x release going to reach it EOF* than CVE fixes FYI: Spring Framework Versions · spring-projects/spring-framework Wiki · GitHub

Re: durable subscribers in artemis cluster

Justin, is the documentation wrong for the boolean values for the legacy forward-when-no-consumers attribute that it associates with STRICT and ON_DEMAND? It seems like STRICT should be false and ON_DEMAND should be true. The problem with message redistribution (just like 5.x's store-and-forward b

Re: durable subscribers in artemis cluster

I do not see that redistribution for STRICT and OFF would solve the problem. The issue I see is the round-robin behavior. If the consumer is disconnected, and queues exists on all nodes, the incoming messages will be round-robined among the nodes. And this means that the consumer must connect to