[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578126#comment-17578126
]
Justin Bertram commented on ARTEMIS-3913:
-----------------------------------------
I just modified the aforementioned tests to use
{{org.eclipse.paho.mqttv5.client.MqttAsyncClient}} and they received the
{{134}} ({{0x86}}) reason code. However, I had to use
{{org.eclipse.paho.mqttv5.client.IMqttToken#waitForCompletion()}} when
connecting otherwise the client wouldn't throw an exception even though the
connection failed.
Regarding the other issues, you'll be best served to open additional Jiras or
better yet send a question to the [ActiveMQ user's mailing
list|https://activemq.apache.org/contact]. Each Jira should focus on a single
issue otherwise it's easy to get things mixed up.
> MQTTReasonCodes byte loss of precision，must int type
> ----------------------------------------------------
>
> Key: ARTEMIS-3913
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3913
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: gongping.zhu
> Priority: Major
> Attachments: image-2022-08-02-08-23-52-965.png,
> image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png,
> image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png,
> image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png,
> image-2022-08-05-08-32-12-492.png
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
