[
https://issues.apache.org/jira/browse/ARTEMIS-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951831#comment-17951831
]
Justin Bertram commented on ARTEMIS-3460:
-----------------------------------------
Can you still reproduce this on the [latest
release|https://activemq.apache.org/components/artemis/download/]? There's been
some work in recent releases dealing with similar sounding use-cases.
> Core bridge - long message payload - JMSCorrelationID filter not working
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-3460
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3460
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.18.0
> Environment: I experienced this behaviour in Artemis MQ 2.16.0 but
> still can be reproduced with 2.18.0
> We use docker images, we have a "central" broker and many "satellite"
> brokers. From the satellite we bridge messages to the central broker where a
> service consume the messages and reply to a given address which is bridged
> back to the sender. Sometimes the length of the reply hit the limit and on
> the satellite broker the original sender can't consume the reply based on the
> JMSCorrelationID. I simplified the environment, so I use the example core
> bridge from apache-artemis-2.18.0-bin (just removed the filter and the
> transform).
> We use Apache.NMS.AMQP in our project but the issue exists with the attached
> AMQP client written in C#, with "ArtemisNetClient" Version="2.2.2" NuGet
> package (in the example the message not acknowledged [hence not deleted from
> the queue] for testing purposes, so it should be deleted manually in order to
> avoid the consumer receive it again on the next start).
> Reporter: Peter Molnar
> Priority: Minor
> Attachments: repro.zip
>
>
> Hi!
> I have an issue, when I send a message which is bridged to another broker.
> The message arrives to the broker (I can see in the management console, if it
> is a "large" message the file appears in the large message directory), but
> * if the length of the payload and the JMSCorrelationID parameter exceeds a
> given number of characters (it is somewhere around 100K, but the issue exists
> with large messages and non-large messages as well) - in the attached example
> client if the message body/payload length is 102309 chars it is working, if
> it is 102310 it is not working!
> * and the message is sent from az AMQP/JMS client (if I send it from
> management console it's working)
> * and the consumer has a filter on JMSCorrelationID field (with other fields
> it is working, so the workaround was to create a custom correlation_id
> property and we use that to filter the message)
> the consumer does not receive the message.
> I tried to add minLargeMessageSize URL parameter both in client and bridge
> connector config, but it does not change the limit (nor the fact the if it is
> more than 100K it is considered as large message regardless the value of the
> parameter, however on management console it says large = false).
> I send the issue to user list, but no solution came up:
> [https://lists.apache.org/thread.html/r6ba7a8769a54db1bf638cae32701b03b9b33b49989b02d726cb14922%40%3Cusers.activemq.apache.org%3E]
> (just workaround what I found)
--
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
