[
https://issues.apache.org/jira/browse/ARTEMIS-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-5220:
------------------------------------
Description:
When using a high available setup, an issue occurs when sending a message with
a header that is too large. The main broker rejects the message, but at the
same time, it seems that it is trying to perform replication to the backup
broker.
The backup broker also rejects this replication message, but after this it
seems that all further messages are blocked. Only after killing the backup
broker, the messages will be processed. Seems like this is related to journal
related operations being blocked until backup acknowledges the completion of
synchronization
(https://activemq.apache.org/components/artemis/documentation/latest/ha.html#replication)
I have included a Quarkus demo app with a description of the scenario, and my
main and backup broker configurations to replicate the issue. Tested against
Artemis version 2.38
Issue sounds similar to issue discussed in ARTEMIS-4694
was:
When using a high available setup, an issue occurs when sending a message with
a header that is too large. The main broker rejects the message, but at the
same time, it seems that it is trying to perform replication to the backup
broker.
The backup broker also rejects this replication message, but after this it
seems that all further messages are blocked. Only after killing the backup
broker, the messages will be processed. Seems like this is related to journal
related operations being blocked until backup acknowledges the completion of
synchronization
(https://activemq.apache.org/components/artemis/documentation/latest/ha.html#replication)
I have included a Quarkus demo app with a description of the scenario, and my
main and backup broker configurations to replicate the issue. Tested against
Artemis version 2.38
Issue sounds similar to issue discussed in
https://issues.apache.org/jira/browse/ARTEMIS-4694
> Messages are blocked after sending too large header
> ---------------------------------------------------
>
> Key: ARTEMIS-5220
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5220
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, Clustering
> Affects Versions: 2.38.0
> Reporter: Thomas Jutten
> Priority: Major
> Attachments: broker-backup.xml, broker-main.xml,
> large-message-error.zip, scenario.txt
>
>
> When using a high available setup, an issue occurs when sending a message
> with a header that is too large. The main broker rejects the message, but at
> the same time, it seems that it is trying to perform replication to the
> backup broker.
> The backup broker also rejects this replication message, but after this it
> seems that all further messages are blocked. Only after killing the backup
> broker, the messages will be processed. Seems like this is related to journal
> related operations being blocked until backup acknowledges the completion of
> synchronization
> (https://activemq.apache.org/components/artemis/documentation/latest/ha.html#replication)
>
> I have included a Quarkus demo app with a description of the scenario, and my
> main and backup broker configurations to replicate the issue. Tested against
> Artemis version 2.38
> Issue sounds similar to issue discussed in ARTEMIS-4694
--
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
