[
https://issues.apache.org/jira/browse/ARTEMIS-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902360#comment-17902360
]
Justin Bertram commented on ARTEMIS-5189:
-----------------------------------------
As noted previously, I recommend you at least try using durable subscriptions
with Artemis. If the problems persist then it would be worth investigating what
the actual bottleneck is and seeing if there are ways to mitigate the issue(s)
with a different configuration.
The behavior you're seeing with non-durable JMS topic subscriptions is expected
and is based on the fundamental semantics of pub/sub style messaging. That
said, you may be able get the semantics you want by using a [retroactive
address|https://activemq.apache.org/components/artemis/documentation/latest/retroactive-addresses.html#retroactive-addresses].
However, before you complicate your configuration I strongly recommend you test
durable subscriptions first.
> Lost messages in non-durable queues during failover
> ---------------------------------------------------
>
> Key: ARTEMIS-5189
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5189
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.38.0
> Reporter: Liviu Citu
> Assignee: Justin Bertram
> Priority: Critical
> Attachments: broker_backup.xml, broker_primary.xml
>
>
> I am currently migrating from Classic Broker to Artemis Broker and I also
> want to enable the Failover (Shared-Stored) switch. I have configured Artemis
> with Failover (Shared-Store) and during the failover switch, topic consumers
> loose events before reconnecting. When using durable consumers this is not
> happening so the problem (as expected) is only replicable for non-durable
> consumers.
> The reason for which I want to avoid using durable consumer is the
> performance impact on the broker side when there is a big number of messages
> and consumers for them. For a live client using Classic Broker I have
> observed a big impact and slowness of the broker under high load (thousands
> of messages with more than 300 durable consumers). Indeed I am not able to
> test the same with Artemis broker as I do not have access to that environment
> however my expectation is that the Artemis broker will behave similarly.
> Is there a parameter in Artemis broker to make it wait a bit after the switch
> before dropping topic message, so that previous active consumers to have
> time to reconnect and consume the messages?
> Attached the Artemis Brokers Primary/Backup configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
