Thanks!
Justin
On Mon, Jul 8, 2024 at 2:49 PM Alexander Milovidov
wrote:
> Done. https://issues.apache.org/jira/browse/ARTEMIS-4911
>
> пн, 8 июл. 2024 г. в 21:22, Justin Bertram :
>
> > The issue you describe with the routed message count looks like a bug.
> Can
> > you open a Jira?
> >
> >
>
Done. https://issues.apache.org/jira/browse/ARTEMIS-4911
пн, 8 июл. 2024 г. в 21:22, Justin Bertram :
> The issue you describe with the routed message count looks like a bug. Can
> you open a Jira?
>
>
> Justin
>
> On Mon, Jul 8, 2024 at 12:43 PM Alexander Milovidov
> wrote:
>
> > Hi Justin,
> >
The issue you describe with the routed message count looks like a bug. Can
you open a Jira?
Justin
On Mon, Jul 8, 2024 at 12:43 PM Alexander Milovidov
wrote:
> Hi Justin,
>
> Thanks for the detailed answer. Of course IBM MQ and ActiveMQ Artemis
> brokers have fundamental differences. I will tr
Hi Justin,
Thanks for the detailed answer. Of course IBM MQ and ActiveMQ Artemis
brokers have fundamental differences. I will try to explain the difference
to the users and instruct them how to send messages.
And it is great that Artemis is in active development. Some users just
don't like any ch
> I think it is based on experience with IBM MQ.
IBM MQ and ActiveMQ Artemis are, of course, 100% independent message broker
implementations. There is overlap in general function and nomenclature, but
past that there are many differences. Expectations will need to be adjusted
accordingly.
> Anoth
> Was it definitely a bug?
Yes. I believe it was.
> As I thought before, the filter is something that stands between address
and queue.
Your assumption here isn't based on how the broker is actually designed.
The filter is actually part of the queue itself. As the documentation [1]
states:
Yeah. Someone complained it as a bug.
We try to keep everything compatible and with an extensive testsuite.
But sometimes it’s not easy to keep everybody happy.
If you need precious semantics we may need to add an address setting.
Clebert Suconic
On Sat, Jul 6, 2024 at 4:23 PM Alexander
I think it is based on experience with IBM MQ. For many years, users have
become accustomed to the fact that a queue is just a queue without any
additional mechanisms such as filters.
In IBM MQ there is no such thing like a filter on the queue.
Another problem for Artemis users is that it is still
I would say it was a bug. Why would you force a send when the filter does
not match ?
Clebert Suconic
On Fri, Jul 5, 2024 at 8:33 AM Alexander Milovidov
wrote:
> Hi All,
>
> Recently I upgraded Artemis to 2.35.0 in the test environment and our
> testers complained that they no longer can send
I also had a strange situation in Artemis 2.32.0 when some messages were
delivered to the multicast queue with redistribution between cluster nodes,
but these messages should not have been delivered (it's properties did not
match the filter). Maybe this fix could help in this situation.
Unfortunate
Hi All,
Recently I upgraded Artemis to 2.35.0 in the test environment and our
testers complained that they no longer can send messages to multicast
queues using FQQN. I have read release notes and found that there was a bug
that was fixed in this version.
Issue https://issues.apache.org/jira/brows
11 matches
Mail list logo
