[
https://issues.apache.org/jira/browse/ARTEMIS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236335#comment-17236335
]
Robbie Gemmell commented on ARTEMIS-2621:
-----------------------------------------
This seems likely to relate to PROTON-2297. It causes failure when a multi-byte
character encoding straddles a frame boundary within a composite buffer. That
could occur sporadically depending on one or all of where the multi-byte chars
were in the body, what frame sizes compose the message, and the size of other
non-body elements in the message are and their effect in turn on the relative
location of where the other bytes end up.
I'll update Artemis to proton-j 0.33.8 along with Qpid JMS 0.55.0 once the
latter is released next week. You could perhaps update proton-j within an
existing broker install to resolve this.
> "IllegalArgumentException: Cannot parse String" when sending large
> String-messages with multi-byte UTF-8-characters
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2621
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2621
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.9.0, 2.11.0
> Reporter: Stefan Kinzel
> Priority: Major
> Attachments: artemis-cannot-parse-string-stacktrace.txt
>
>
> These Exceptions appear sporadically while sending large text-messages
> containing multi-byte UTF-8-characters to the broker.
> The behaviour is reproducible by sending large (5MB) text-messages containing
> only two-byte-characters to an artemis-broker.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
