[jira] [Commented] (ARTEMIS-2621) "IllegalArgumentException: Cannot parse String" when sending large String-messages with multi-byte UTF-8-characters

2020-11-20 Thread Robbie Gemmell (Jira)


[ 
https://issues.apache.org/jira/browse/ARTEMIS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236339#comment-17236339
 ] 

Robbie Gemmell commented on ARTEMIS-2621:
-

Noting though that I believe the message behaviour changed and this originally 
occurred while converting the messages into a Core message internally to store 
it, which always happened for large AMQP messages previously but doesn't now 
and so wont it neednt decode the body, meaning this probably wouldn't be hit as 
originally seen when using newer brokers except when doing a 
protocol-conversion.

> "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
> Fix For: 2.17.0
>
> 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)


[jira] [Commented] (ARTEMIS-2621) "IllegalArgumentException: Cannot parse String" when sending large String-messages with multi-byte UTF-8-characters

2020-11-20 Thread Robbie Gemmell (Jira)


[ 
https://issues.apache.org/jira/browse/ARTEMIS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (ARTEMIS-2621) "IllegalArgumentException: Cannot parse String" when sending large String-messages with multi-byte UTF-8-characters

2020-02-14 Thread Robbie Gemmell (Jira)


[ 
https://issues.apache.org/jira/browse/ARTEMIS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036864#comment-17036864
 ] 

Robbie Gemmell commented on ARTEMIS-2621:
-

You say its reproducible so please provide the reproducer. It would make it far 
easier for people to investigate exactly what you are hitting rather than 
burning time needlessly trying to match it, while guessing if they are, and 
also more likely people might be able to fit investigating it into their 
limited schedules.

Note: using the the updated proton-j from the linked Jira to including the 
causing exception may also help when someone does investigate.

> "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)