Hi Matt,
So yeah that's pretty much what I'm trying to figure out as well, or more
specifically why it is looking for that pattern instead of the actual
configured pattern. To better explain the scenario, there's 2 versions of the
app, V1 & V2. They look like this:
V1:
- Consumes from Consum
Hi John-
The error message seems to indicate the app is using a wild card subscription
(or getting one encoded funny), but the authz is named to a specific
destinations
\u003e = “>"
What you have should work fine, but there seems to be a coordination problem.
Either the authz needs the “>” wi
Hi there
We're on "Classic" 5.17.2 and use VirtualTopics pretty heavily, due to some
external constraints can't use Artemis quite yet. I was wondering, is
there any guidance on setting up ACLs with VirtualTopics?
Originally when we setup the connection, the application was connecting and
consumi
Hello,
I've observed a somewhat unexpected behavior of message delivery after a
recover with the following setup:
- Artemis broker (tested with 2.24.0 and 3.0.0)
- JMSConsumer (shared durable) *C* with
*ActiveMQJMSConstants.INDIVIDUAL_ACKNOWLEDGE*
- JMSProducer (shared durable) *P*
