[
https://issues.apache.org/jira/browse/ARTEMIS-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880365#comment-17880365
]
Tom Tichy edited comment on ARTEMIS-5040 at 9/9/24 2:56 PM:
------------------------------------------------------------
Yes, it just keeps throwing AMQ850000 code ..
With persistence disabled and with persistence disabled for subscriptions, it
fails graciously. I.e. there are failures on the client(s) side, but the broker
stays functional.
was (Author: JIRAUSER305154):
Yes, it just keeps throwing AMQ850000 code ..
With persistence disabled, it fails graciously. I.e. there are failures on the
client(s) side, but the broker stays functional.
> Improve Failure mode when handling a burst of incoming connections
> ------------------------------------------------------------------
>
> Key: ARTEMIS-5040
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5040
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.37.0
> Environment: 2.37.00 running in Docker
> Reporter: Tom Tichy
> Priority: Major
>
> I have a few thousand of badly behaving IoT clients that connect at the same
> time.
> Artemis starts throwing "AMQ850000: Unable to store MQTT state within given
> timeout: 5000ms", which is understandable.
> What is not ideal is that even after the burst of incoming connection stops,
> the broker gets into a state where it is effectively not functional for the
> next 10-15 minutes. It just continues to throw exceptions and is unable to
> function.
> I have done some testing with other brokers. They fail as well, but after the
> connection burst stops, they recover immediately and continue to function.
> That would be the desired behavior for Artemis as well.
> (Apache Jmeter jmx file available)
--
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
