[
https://issues.apache.org/jira/browse/PROTON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035519#comment-17035519
]
Robbie Gemmell commented on PROTON-2179:
----------------------------------------
If the same message doesn't produce the same issue consistently, it seems more
likely that the issue isnt proton-j but in the broker (or client). The
exception being thrown is based on an originating failure from a CharsetDecoder
rather than in proton-j itself and so suggests an issue with the delivery
payload, or perhaps how it is being accessed in the broker. Without any any
more detail on the payload there is little to look at in proton-j itself
currently.
Having the exception carry its actual cause would be useful though, and I have
just made that change.
Perhaps you can try using that in your env to see if it aids your diagnosis.
Similarly you might try looking at the message payload actually sent+received
(e.g inspect with wireshark) to observe that its as expected.
> Include exception cause when String parse fails
> -----------------------------------------------
>
> Key: PROTON-2179
> URL: https://issues.apache.org/jira/browse/PROTON-2179
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.33.2
> Environment: Broker: apache-artemis-2.11.0, apache-artemis-2.9.0
> Client: qpid-jms 0.48.0
> Reporter: Stefan Kinzel
> Priority: Trivial
> Attachments: artemis-cannot-parse-string-stacktrace.txt
>
>
> These exceptions appear sporadically while sending Text-Messages (JSON) from
> a qpid-jms-client to an apache artemis message-broker. They can not be
> reproduced using the same message: A second attempt mostly works.
> A stacktrace is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
