Perhaps it helps to understand that Topics never store messages themselves
- topic subscriptions store messages. This includes non-persistent
messages stored in memory.
So if there is a send to a topic that has no subscriptions, whether durable
or non-durable, the message ends up discarded.
Art
It's likely the cause of the problem is timing of the matching on the
subscription pattern - does the second topic exist when the subscription is
created?
I know how this operates for JMS, and composites work that way - when the
subscription to a composite is created, then the list of actual
You could potentially reproduce the problem on a locally running community
release of ActiveMQ "Classic." That wouldn't be too hard, I think. Then
you'd know for sure the problem wasn't introduced via AmazonMQ, and the
community would be more able to help.
Justin
On Tue, Aug 1, 2023 at 9:25 AM
Hi John-
Best to contact AWS support. ActiveMQ project has no way of knowing what
changes they have made.
Thanks,
Matt Pavlovich
> On Aug 1, 2023, at 9:24 AM, John Damon wrote:
>
> Hey,
>
> I’ve been spinning my wheels on this and was hoping someone could help me
> understand the mistakes
Hey,
I’ve been spinning my wheels on this and was hoping someone could help me
understand the mistakes I’m making. Here’s some background:
* Using AmazonMQ for ActiveMQ
* Publisher is publishing messages to my broker using MQTT protocol using
QoS 1 (written in java)
* Subscriber
