Re: Unable to connect topic queue with below configuration

2024-05-03 Thread Justin Bertram
FYI - I opened ARTEMIS-4760 [1] for this issue. I'll send a PR with a fix soon. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-4760 On Fri, May 3, 2024 at 12:46 PM Justin Bertram wrote: > I believe this is a bug in the MQTT implementation. As noted in the > documentation [1]: > > >

Re: Unable to connect topic queue with below configuration

2024-05-03 Thread Justin Bertram
MQTT is fundamentally a pub/sub protocol so it doesn't really match with JMS queue semantics which are point-to-point. STOMP might be a better choice for you from Angular. Is there a specific reason you are mixing JMS queue and MQTT? Justin On Sat, May 4, 2024 at 12:11 AM Pushparaj

Re: Unable to connect topic queue with below configuration

2024-05-03 Thread Pushparaj Chinnathambi
Dear Justin, I appreciate your attention to this issue. Now, I will explain my overall scenario. I'm using JMS to produce notifications for my end-users to remind them of certain actions. This JMS (in spring boot) sends messages to the ALERTS queue. I need to write a consumer to listen to

Re: question on message-redistribution in an Artemis cluster

2024-05-03 Thread Justin Bertram
Where exactly do you see the re-ordering of messages and how are you determining that they are, in fact, re-ordered? Are they re-ordered in the target queue itself or on the consumer(s)? Do you have a way that I can reproduce this behavior? If I recall correctly there is just one thread that

Re: Stomp acceptor causes address memory rise

2024-05-03 Thread Justin Bertram
Have you conclusively determined that the STOMP acceptor is _causing_ the difference? If so, do you have a test to reproduce this behavior? Perhaps this is just a coincidence? > Is the Messagebuffer to high? I'm not sure what you mean by "Messagebuffer." Can you clarify? Justin On Fri, May

Re: Unable to connect topic queue with below configuration

2024-05-03 Thread Justin Bertram
I believe this is a bug in the MQTT implementation. As noted in the documentation [1]: > Automatic queue creation is for queues that would not otherwise be created during normal operation. However, the MQTT implementation is deciding on whether to create the subscription queue based on the

Re: Request to join ActiveMQ Slack channel

2024-05-03 Thread Justin Bertram
Done. Justin On Fri, May 3, 2024 at 12:28 PM Jerry Zou wrote: > Hi, > > Can I please request an invitation to the ActiveMQ slack channel for > jerryzoub...@gmail.com? > > Thanks in advance > > Best, > Jerry >

Request to join ActiveMQ Slack channel

2024-05-03 Thread Jerry Zou
Hi, Can I please request an invitation to the ActiveMQ slack channel for jerryzoub...@gmail.com? Thanks in advance Best, Jerry

Stomp acceptor causes address memory rise

2024-05-03 Thread Herbert . Helmstreit
Hello Community in an artemis 2.33 cluster with relatively high rate of core messages we enabled a stomp acceptor on one broker. Compared to the other brokers in the cluster that have <1 MiB used Address Memory the modified guy goes up to 250 MiB. There is no stomp client attached. The value

question on message-redistribution in an Artemis cluster

2024-05-03 Thread Dondorp, Erwin
Intern Hello, I have an Artemis cluster with several nodes. In many cases, messages arrive on one node and are consumed from another node. The cluster-connections between the nodes do their work to make that happen. But under high-load we see messages being re-ordered between the broker-nodes,

Re: Reg, How to subscribe already created queue using MQQT

2024-05-03 Thread Vaclav Haisman
On Fri, May 3, 2024 at 2:14 PM Balamurugan Ranganathan < rbalamurugant...@gmail.com> wrote: > Dear All, > > I have configured Artemis and created an address & topic using the console. > > Address --> *UI* > Queue --> *ALERTS* (ANYCAST,MULTICAST). > > In backend (using java 21) I am able to

Reg, How to subscribe already created queue using MQQT

2024-05-03 Thread Balamurugan Ranganathan
Dear All, I have configured Artemis and created an address & topic using the console. Address --> *UI* Queue --> *ALERTS* (ANYCAST,MULTICAST). In backend (using java 21) I am able to access the queue name as *UI::ALERTS.* But using ANGULAR (ngx-mqtt ) It shows an error message as *Queue does

AW: Suspected slow replication

2024-05-03 Thread Arno Schuerhoff
Hello Justin, I believe I have found a part where an additional header is added: org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl (Line 108, Tag 2.31.2) if (!coreMessage.containsProperty(Message.HDR_LARGE_BODY_SIZE)) {

Re: ClassCastException in ConfigurationUtils.getHAPolicy

2024-05-03 Thread Bernd Köcke
Hello Justin, thanks a lot for the ticket and your work! Regards Bernd Am 03.05.24 um 06:54 schrieb Justin Bertram: I opened ARTEMIS-4759 [1] to deal with this and sent a PR. Thanks for the report! Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-4759 On Wed, Apr 24, 2024 at 9:33