[jira] [Reopened] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu reopened ARTEMIS-4519: --- A third-party mqtt client successfully connects to ActiveMQ Artemis. The server generates two sessions, one for regular client operations and the other for internal management operations. Based on your conclusion, I tracked and reviewed the source code and found that the session names used for internal management start with management::, but none of them I saw in the web management console, And there are no sessions starting with management:: on the backend log, what's going on? Can anyone help answer this? > Why can a client connect and see two different session IDs on the console? > -- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.31.2 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791852#comment-17791852 ] gongping.zhu commented on ARTEMIS-4519: --- thx a lot > Why can a client connect and see two different session IDs on the console? > -- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.31.2 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791417#comment-17791417 ] gongping.zhu edited comment on ARTEMIS-4519 at 11/30/23 3:02 AM: - when i nomally use ./artemis create /var/www/html/brokers/node3 to create instance;and then use ./artemis run; after zhe broker started,i use zhe third mqtt client to connect zhe broker, and login zhe web admin console,you can see this one connect has two different session !image-2023-11-30-11-00-08-171.png! was (Author: JIRAUSER293605): when i nomally use ./artemis create /var/www/html/brokers/node3 to create instance;and then use ./artemis run; after zhe broker started,i use zhe third mqtt client to connect zhe broker, and login zhe web admin console,you can see this !image-2023-11-30-11-00-08-171.png! > Why can a client connect and see two different session IDs on the console? > -- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.31.2 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-4519: -- Attachment: image-2023-11-30-11-00-08-171.png > Why can a client connect and see two different session IDs on the console? > -- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.31.2 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791417#comment-17791417 ] gongping.zhu commented on ARTEMIS-4519: --- when i nomally use ./artemis create /var/www/html/brokers/node3 to create instance;and then use ./artemis run; after zhe broker started,i use zhe third mqtt client to connect zhe broker, and login zhe web admin console,you can see this !image-2023-11-30-11-00-08-171.png! > Why can a client connect and see two different session IDs on the console? > -- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT >Affects Versions: 2.31.2 >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?
gongping.zhu created ARTEMIS-4519: - Summary: Why can a client connect and see two different session IDs on the console? Key: ARTEMIS-4519 URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 Project: ActiveMQ Artemis Issue Type: Bug Components: MQTT Affects Versions: 2.31.2 Reporter: gongping.zhu Why can a client connect and see two different session IDs on the console? After a successful client connection, it will call before Create Session twice, with the same connId but different sessions? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-4156: -- Affects Version/s: 2.27.1 > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0, 2.27.1 > Environment: When I deploy the plugin developed using spring-related > components to artemis, the system can perform authentication and > authentication normally, and can authenticate clientId normally, but its > management console cannot be used normally, and an error message of no > permission is always reported, such as: could not invoke list > connectionsjava.lang.Exception: User not authorized to access operation: > listConnections >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
[ https://issues.apache.org/jira/browse/ARTEMIS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-4156: -- Environment: When I deploy the plugin developed using spring-related components to artemis, the system can perform authentication and authentication normally, and can authenticate clientId normally, but its management console cannot be used normally, and an error message of no permission is always reported, such as: could not invoke list connectionsjava.lang.Exception: User not authorized to access operation: listConnections (was: When I deploy the developed plugin to artemis, the system can perform authentication and authentication normally, and the clientId can be authenticated normally, but its management console cannot be used normally, and it keeps reporting an error message that there is no permission, such as: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections) > could not invoke list connectionsjava.lang.Exception : User not authorized to > access operation: listConnections > --- > > Key: ARTEMIS-4156 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0 > Environment: When I deploy the plugin developed using spring-related > components to artemis, the system can perform authentication and > authentication normally, and can authenticate clientId normally, but its > management console cannot be used normally, and an error message of no > permission is always reported, such as: could not invoke list > connectionsjava.lang.Exception: User not authorized to access operation: > listConnections >Reporter: gongping.zhu >Priority: Major > Attachments: image-2023-02-06-11-52-29-213.png > > > !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4156) could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections
gongping.zhu created ARTEMIS-4156: - Summary: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections Key: ARTEMIS-4156 URL: https://issues.apache.org/jira/browse/ARTEMIS-4156 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.26.0 Environment: When I deploy the developed plugin to artemis, the system can perform authentication and authentication normally, and the clientId can be authenticated normally, but its management console cannot be used normally, and it keeps reporting an error message that there is no permission, such as: could not invoke list connectionsjava.lang.Exception : User not authorized to access operation: listConnections Reporter: gongping.zhu Attachments: image-2023-02-06-11-52-29-213.png !image-2023-02-06-11-52-29-213.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4097) Can I listen to the device connection and disconnection events in the activemq artemis plug-in and send the corresponding mqtt message, if yes, how to do it?
gongping.zhu created ARTEMIS-4097: - Summary: Can I listen to the device connection and disconnection events in the activemq artemis plug-in and send the corresponding mqtt message, if yes, how to do it? Key: ARTEMIS-4097 URL: https://issues.apache.org/jira/browse/ARTEMIS-4097 Project: ActiveMQ Artemis Issue Type: Wish Components: ActiveMQ-Artemis-Native Affects Versions: 2.26.0 Reporter: gongping.zhu Assignee: Clebert Suconic Can I listen to the device connection and disconnection events in the activemq artemis plug-in and send the corresponding mqtt message, if yes, how to do it? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4036) mqtt client receive 131 code
[ https://issues.apache.org/jira/browse/ARTEMIS-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627534#comment-17627534 ] gongping.zhu commented on ARTEMIS-4036: --- 2022-11-01 13:54:48,205 ERROR [org.apache.activemq.artemis.core.server] AMQ224096: Error setting up connection from /47.101.154.149:55358 to /172.22.35.99:5672; protocol CORE not found in map: [AMQP] 2022-11-01 13:54:48,205 ERROR [org.apache.activemq.artemis.core.server] AMQ224096: Error setting up connection from /47.101.154.149:38734 to /172.22.35.99:1883; protocol CORE not found in map: [MQTT] 2022-11-01 17:04:19,146 ERROR [org.apache.activemq.artemis.core.server] AMQ224096: Error setting up connection from /101.133.147.20:41770 to /172.22.35.99:61613; protocol CORE not found in map: [STOMP] 2022-11-01 17:37:17,198 WARN [org.apache.activemq.artemis.core.server] AMQ222107: Cleared up resources for session c6313c66-59c8-11ed-a15c-aeb104d0d5a5 2022-11-01 17:37:17,198 WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection failed, clearing up resources for session c6313c67-59c8-11ed-a15c-aeb104d0d5a5 > mqtt client receive 131 code > > > Key: ARTEMIS-4036 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4036 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > > sometimes mqtt client connect the server ; it will receive The Server > Disconnected the client. Disconnect RC: 131 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4080) mqtt client receive 131 code
gongping.zhu created ARTEMIS-4080: - Summary: mqtt client receive 131 code Key: ARTEMIS-4080 URL: https://issues.apache.org/jira/browse/ARTEMIS-4080 Project: ActiveMQ Artemis Issue Type: Bug Components: ActiveMQ-Artemis-Native Affects Versions: 2.26.0 Reporter: gongping.zhu Assignee: Clebert Suconic Recently, it has been found that some devices have successfully connected to the Artemis 2.26.0 version service. After a period of time, the device has not been able to connect to the service. At the same time, the client receives The Server Disconnected the Client, RC 131. Can you help diagnose and analyze the reason? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4046) mqtt $share topic can not work
[ https://issues.apache.org/jira/browse/ARTEMIS-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17617433#comment-17617433 ] gongping.zhu commented on ARTEMIS-4046: --- when i upgrade 2.26.0 and use MQTT.x[v1.8.3] client tool to connect server; and sub topic $share/hello/hello/# it cannot work right; after i chg to 2.25.0 it can work right > mqtt $share topic can not work > -- > > Key: ARTEMIS-4046 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4046 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.26.0 >Reporter: gongping.zhu >Priority: Major > > When I use version 2.25.0, I can correctly use the share topic mechanism; > When I upgrade to 2.26.0, the share topic mechanism cannot work； > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4046) mqtt $share topic can not work
gongping.zhu created ARTEMIS-4046: - Summary: mqtt $share topic can not work Key: ARTEMIS-4046 URL: https://issues.apache.org/jira/browse/ARTEMIS-4046 Project: ActiveMQ Artemis Issue Type: Bug Components: AMQP Affects Versions: 2.26.0 Reporter: gongping.zhu When I use version 2.25.0, I can correctly use the share topic mechanism; When I upgrade to 2.26.0, the share topic mechanism cannot work； -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4036) mqtt client receive 131 code
gongping.zhu created ARTEMIS-4036: - Summary: mqtt client receive 131 code Key: ARTEMIS-4036 URL: https://issues.apache.org/jira/browse/ARTEMIS-4036 Project: ActiveMQ Artemis Issue Type: Bug Components: ActiveMQ-Artemis-Native Affects Versions: 2.25.0 Reporter: gongping.zhu Assignee: Clebert Suconic sometimes mqtt client connect the server ; it will receive The Server Disconnected the client. Disconnect RC: 131 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Attachment: (was: image-2022-08-26-13-06-42-209.png) > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log > > > under network jitter sendWillMessage will cause java.lang.StackOverflowError > > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Description: under network jitter sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline was: under network jitter sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log > > > under network jitter sendWillMessage will cause java.lang.StackOverflowError > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Description: under network jitter sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline was: under network jitter !image-2022-08-26-13-06-42-209.png|width=16,height=16,id=dimg_3! sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log, image-2022-08-26-13-06-42-209.png > > > under network jitter sendWillMessage will cause java.lang.StackOverflowError > > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Summary: network jitter sendWillMessage will cause java.lang.StackOverflowError (was: network network instability sendWillMessage will cause java.lang.StackOverflowError) > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log, image-2022-08-26-13-06-42-209.png > > > under network network instability sendWillMessage will cause > java.lang.StackOverflowError > > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Description: under network jitter !image-2022-08-26-13-06-42-209.png|width=16,height=16,id=dimg_3! sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline was: under network network instability sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log, image-2022-08-26-13-06-42-209.png > > > under > network jitter > !image-2022-08-26-13-06-42-209.png|width=16,height=16,id=dimg_3! > sendWillMessage will cause java.lang.StackOverflowError > > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3958) network jitter sendWillMessage will cause java.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/ARTEMIS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3958: -- Attachment: image-2022-08-26-13-06-42-209.png > network jitter sendWillMessage will cause java.lang.StackOverflowError > -- > > Key: ARTEMIS-3958 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > Attachments: StackOverflowError.log, image-2022-08-26-13-06-42-209.png > > > under network network instability sendWillMessage will cause > java.lang.StackOverflowError > > it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3958) network network instability sendWillMessage will cause java.lang.StackOverflowError
gongping.zhu created ARTEMIS-3958: - Summary: network network instability sendWillMessage will cause java.lang.StackOverflowError Key: ARTEMIS-3958 URL: https://issues.apache.org/jira/browse/ARTEMIS-3958 Project: ActiveMQ Artemis Issue Type: Bug Components: ActiveMQ-Artemis-Native Affects Versions: 2.25.0 Reporter: gongping.zhu Assignee: Clebert Suconic Attachments: StackOverflowError.log under network network instability sendWillMessage will cause java.lang.StackOverflowError it will cause the device to switch back and forth between online and offline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu edited comment on ARTEMIS-3953 at 8/23/22 7:20 AM:
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
after upgrade maven version to 3.8.6 problem solve
was (Author: JIRAUSER293605):
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
after upgrade maven version to 3.8.6 problem still exist
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu edited comment on ARTEMIS-3953 at 8/23/22 7:01 AM:
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
after upgrade maven version to 3.8.6 problem still exist
was (Author: JIRAUSER293605):
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
compile passed after upgrade maven version to 3.8.6
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu edited comment on ARTEMIS-3953 at 8/23/22 6:59 AM:
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
compile passed after upgrade maven version to 3.8.6
was (Author: JIRAUSER293605):
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu edited comment on ARTEMIS-3953 at 8/23/22 6:28 AM:
when outside IDEA it still can't compile
and the error as below,the version is Apache Maven 3.6.2
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (fallback-javadoc-jar)
on project artemis-website: MavenReportException: Error while generating
Javadoc: Unable to find javadoc command: The environment variable JAVA_HOME is
not correctly set.
was (Author: JIRAUSER293605):
when outside IDEA it still can't
the version is Apache Maven 3.6.2
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu commented on ARTEMIS-3953:
---
when outside IDEA it still can't
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583390#comment-17583390
]
gongping.zhu commented on ARTEMIS-3953:
---
when outside IDEA it still can't
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583391#comment-17583391
]
gongping.zhu edited comment on ARTEMIS-3953 at 8/23/22 6:25 AM:
when outside IDEA it still can't
the version is Apache Maven 3.6.2
was (Author: JIRAUSER293605):
when outside IDEA it still can't
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583379#comment-17583379 ] gongping.zhu commented on ARTEMIS-3952: --- bootstrap.xml http://activemq.apache.org/schema;> http://localhost:8161;> > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583374#comment-17583374 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 5:50 AM: broker.xml http://www.w3.org/2001/XMLSchema-instance; xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="urn:activemq:core "> brokernode false NIO data/paging data/bindings data/journal data/large-messages true 2 10 4096 10M 13596000 1 5000 90 true 12 6 HALT 13596000 -1 tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true tcp://0.0.0.0:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true;directDeliver=false;anycastPrefix=$share/; DLQ ExpiryQueue 0 -1 10 PAGE true true DLQ ExpiryQueue 0 -1 -1 10 PAGE true true false false was (Author: JIRAUSER293605): http://www.w3.org/2001/XMLSchema-instance; xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="urn:activemq:core "> brokernode false NIO data/paging data/bindings data/journal data/large-messages true 2 10 4096 10M 13596000 1 5000 90 true 12 6 HALT 13596000 -1 tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true tcp://0.0.0.0:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true;directDeliver=false;anycastPrefix=$share/; DLQ ExpiryQueue 0 -1 10 PAGE true true DLQ ExpiryQueue 0 -1 -1 10 PAGE true true false false > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583374#comment-17583374 ] gongping.zhu commented on ARTEMIS-3952: --- http://www.w3.org/2001/XMLSchema-instance; xmlns:xi="http://www.w3.org/2001/XInclude; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="urn:activemq:core "> brokernode false NIO data/paging data/bindings data/journal data/large-messages true 2 10 4096 10M 13596000 1 5000 90 true 12 6 HALT 13596000 -1 tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true tcp://0.0.0.0:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true;directDeliver=false;anycastPrefix=$share/; DLQ ExpiryQueue 0 -1 10 PAGE true true DLQ ExpiryQueue 0 -1 -1 10 PAGE true true false false > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583327#comment-17583327 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 3:51 AM: beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool [eg:mqtt.fx-1.7.1] to connect and when LWT message afterSend finished and authenticate will be recall; 1,connect to zhe mqtt service; it can see beforeCreateSession will be call two times 2,Unplug the device network cable，and u can see authenticate will be call two times here is zhe log 2022-08-23 11:45:40,908 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:45:40,909 INFO [monitor] beforeCreateSession 2022-08-23 11:45:40,967 INFO [monitor] 连接成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 1 1 2022-08-23 11:45:40,968 INFO [monitor] beforeCreateSession 2022-08-23 11:47:12,251 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,282 INFO [monitor] 断开成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 LWT 1 2022-08-23 11:47:12,286 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,300 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate was (Author: JIRAUSER293605): beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool [eg:mqtt.fx-1.7.1] to connect and when LWT message afterSend finished and authenticate will be recall; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583327#comment-17583327 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 3:51 AM: beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool [eg:mqtt.fx-1.7.1] to connect and when LWT message afterSend finished and authenticate will be recall; 1,connect to zhe mqtt service; it can see beforeCreateSession will be call two times 2,Unplug the device network cable，and u can see authenticate will be call three times here is zhe log 2022-08-23 11:45:40,908 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:45:40,909 INFO [monitor] beforeCreateSession 2022-08-23 11:45:40,967 INFO [monitor] 连接成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 1 1 2022-08-23 11:45:40,968 INFO [monitor] beforeCreateSession 2022-08-23 11:47:12,251 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,282 INFO [monitor] 断开成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 LWT 1 2022-08-23 11:47:12,286 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,300 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate was (Author: JIRAUSER293605): beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool [eg:mqtt.fx-1.7.1] to connect and when LWT message afterSend finished and authenticate will be recall; 1,connect to zhe mqtt service; it can see beforeCreateSession will be call two times 2,Unplug the device network cable，and u can see authenticate will be call two times here is zhe log 2022-08-23 11:45:40,908 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:45:40,909 INFO [monitor] beforeCreateSession 2022-08-23 11:45:40,967 INFO [monitor] 连接成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 1 1 2022-08-23 11:45:40,968 INFO [monitor] beforeCreateSession 2022-08-23 11:47:12,251 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,282 INFO [monitor] 断开成功 BLB10Y2020A040422010009@02:00:00:0e:1f:01 10.18.9.150:58316 b0b35376 LWT 1 2022-08-23 11:47:12,286 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:47:12,300 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583327#comment-17583327 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 3:42 AM: beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool [eg:mqtt.fx-1.7.1] to connect and when LWT message afterSend finished and authenticate will be recall; was (Author: JIRAUSER293605): beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool to connect and when LWT message afterSend finished and authenticate will be recall; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583327#comment-17583327 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 3:41 AM: beforeCreateSession call mult times, uncoment zhe biz code,keep zhe log code; and zip file to broker/lib;and use ./artemis-service restart; when it start finished,you can use the third client tool to connect and when LWT message afterSend finished and authenticate will be recall; was (Author: JIRAUSER293605): beforeCreateSession call mult times and when LWT message afterSend finished and authenticate will be recall; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583327#comment-17583327 ] gongping.zhu commented on ARTEMIS-3952: --- beforeCreateSession call mult times and when LWT message afterSend finished and authenticate will be recall; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583312#comment-17583312 ] gongping.zhu edited comment on ARTEMIS-3952 at 8/23/22 3:15 AM: i attach zhe code; and below is zhe run log 2022-08-23 11:12:14,065 INFO [com.yeker.iot.broker.plugin.impl.JAASSecurityManagerWrapper] authenticate 2022-08-23 11:12:14,168 INFO [monitor] beforeCreateSession 2022-08-23 11:12:14,315 INFO [monitor] 连接成功 0-YK00Y3030A04042202@b813320e52ad 127.0.0.1:56224 ff4f06b3 1 1 2022-08-23 11:12:14,332 INFO [monitor] beforeCreateSession was (Author: JIRAUSER293605): i attach zhe code; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3952: -- Attachment: ArtemisBrokerPlugin.java JAASSecurityManagerWrapper.java > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583312#comment-17583312 ] gongping.zhu commented on ARTEMIS-3952: --- i attach zhe code; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952 ] gongping.zhu deleted comment on ARTEMIS-3952: --- was (Author: JIRAUSER293605): i attach zhe code; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583313#comment-17583313 ] gongping.zhu commented on ARTEMIS-3952: --- i attach zhe code; > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ArtemisBrokerPlugin.java, JAASSecurityManagerWrapper.java > > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3953) project compile failed on mac
[
https://issues.apache.org/jira/browse/ARTEMIS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gongping.zhu updated ARTEMIS-3953:
--
Affects Version/s: 2.25.0
> project compile failed on mac
> --
>
> Key: ARTEMIS-3953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.25.0
>Reporter: gongping.zhu
>Priority: Major
>
> when i git clone zhe project and import the IDEA, it can not success use
> maven to compile;
>
> it need add zhe below element for each maven-javadoc-plugin configuation
> ${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-3953) project compile failed on mac
gongping.zhu created ARTEMIS-3953:
-
Summary: project compile failed on mac
Key: ARTEMIS-3953
URL: https://issues.apache.org/jira/browse/ARTEMIS-3953
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: gongping.zhu
when i git clone zhe project and import the IDEA, it can not success use maven
to compile;
it need add zhe below element for each maven-javadoc-plugin configuation
${java.home}/bin/javadoc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3951) when i develop a plugin to auth not empty client_ID，Artemis cannot renturn invalidate client_ID reason code
[ https://issues.apache.org/jira/browse/ARTEMIS-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583306#comment-17583306 ] gongping.zhu edited comment on ARTEMIS-3951 at 8/23/22 2:51 AM: because my code does not merge in to master,may you can imp it was (Author: JIRAUSER293605): because my code does not merge in to master > when i develop a plugin to auth not empty client_ID，Artemis cannot renturn > invalidate client_ID reason code > --- > > Key: ARTEMIS-3951 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3951 > Project: ActiveMQ Artemis > Issue Type: Wish >Reporter: gongping.zhu >Priority: Major > > when i develop a plugin to auth not empty client_ID，Artemis cannot renturn > invalidate client_ID reason code，it just return wrong user password reason > code，can u return invalid -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3951) when i develop a plugin to auth not empty client_ID，Artemis cannot renturn invalidate client_ID reason code
[ https://issues.apache.org/jira/browse/ARTEMIS-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583306#comment-17583306 ] gongping.zhu commented on ARTEMIS-3951: --- because my code does not merge in to master > when i develop a plugin to auth not empty client_ID，Artemis cannot renturn > invalidate client_ID reason code > --- > > Key: ARTEMIS-3951 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3951 > Project: ActiveMQ Artemis > Issue Type: Wish >Reporter: gongping.zhu >Priority: Major > > when i develop a plugin to auth not empty client_ID，Artemis cannot renturn > invalidate client_ID reason code，it just return wrong user password reason > code，can u return invalid -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
[ https://issues.apache.org/jira/browse/ARTEMIS-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3952: -- Affects Version/s: 2.25.0 > when auth plugin called, beforeCreateSession method will be call twice time > --- > > Key: ARTEMIS-3952 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: gongping.zhu >Priority: Major > > 1, when auth plugin called,the beforeCreateSession method will be call twice > times > 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3952) when auth plugin called, beforeCreateSession method will be call twice time
gongping.zhu created ARTEMIS-3952: - Summary: when auth plugin called, beforeCreateSession method will be call twice time Key: ARTEMIS-3952 URL: https://issues.apache.org/jira/browse/ARTEMIS-3952 Project: ActiveMQ Artemis Issue Type: Bug Reporter: gongping.zhu 1, when auth plugin called,the beforeCreateSession method will be call twice times 2,ActiveMQSecurityManager5 authenticate method will call more then one times -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3951) when i develop a plugin to auth not empty client_ID，Artemis cannot renturn invalidate client_ID reason code
gongping.zhu created ARTEMIS-3951: - Summary: when i develop a plugin to auth not empty client_ID，Artemis cannot renturn invalidate client_ID reason code Key: ARTEMIS-3951 URL: https://issues.apache.org/jira/browse/ARTEMIS-3951 Project: ActiveMQ Artemis Issue Type: Wish Reporter: gongping.zhu when i develop a plugin to auth not empty client_ID，Artemis cannot renturn invalidate client_ID reason code，it just return wrong user password reason code，can u return invalid -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3948) artemis 2.24.x LWT message send,it cannot invoke before or after Send method and i just invoke xxxMessageRoute method and i can't get zhe correspond remoteConnection;
[
https://issues.apache.org/jira/browse/ARTEMIS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583188#comment-17583188
]
gongping.zhu commented on ARTEMIS-3948:
---
thx a lot，when it will release
回复的原邮件
[
https://issues.apache.org/jira/browse/ARTEMIS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583183#comment-17583183
]
Justin Bertram 在 ARTEMIS-3948中留言:
-
I'm closing this as I changed the way LWT messages are sent via ARTEMIS-3942.
You can get the connection from the {{ServerSession}} passed into
{{o.a.a.a.c.s.p.ActiveMQServerMessagePlugin#beforeSend(ServerSession,
Transaction, Message, boolean, boolean)}} now for LWT messages.
I don't totally understand your requirement as the English doesn't make much
sense, but I'm hopeful this will resolve your problem.
--
这条信息是由Atlassian Jira发送的
(v8.20.10#820010)
> artemis 2.24.x LWT message send,it cannot invoke before or after Send method
> and i just invoke xxxMessageRoute method and i can't get zhe correspond
> remoteConnection;
> --
>
> Key: ARTEMIS-3948
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3948
> Project: ActiveMQ Artemis
> Issue Type: Wish
>Affects Versions: 2.24.0
>Reporter: gongping.zhu
>Priority: Major
>
> i want develop a plugin to catch zhe LWT message and get zhe correspond
> remoteConnection;
> after 2.24.x it can't do;
> can u expose zhe remoteConnection when route LWT mesage?
> if u not do zhis ,it will case connect state not correct; when lwt message
> not process in time,and new connect it wil case wrong state
>
> but apache-activemq-5.16.4 version send LWT message can get remote connect id
> use
> ProducerBrokerExchange
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3948) artemis 2.24.x LWT message send,it cannot invoke before or after Send method and i just invoke xxxMessageRoute method and i can't get zhe correspond remoteConnection;
[ https://issues.apache.org/jira/browse/ARTEMIS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3948: -- Description: i want develop a plugin to catch zhe LWT message and get zhe correspond remoteConnection; after 2.24.x it can't do; can u expose zhe remoteConnection when route LWT mesage? if u not do zhis ,it will case connect state not correct; when lwt message not process in time,and new connect it wil case wrong state but apache-activemq-5.16.4 version send LWT message can get remote connect id was: i want develop a plugin to catch zhe LWT message and get zhe correspond remoteConnection; after 2.24.x it can't do; can u expose zhe remoteConnection when route LWT mesage? if u not do zhis ,it will case connect state not correct; when lwt message not process in time,and new connect it wil case wrong state > artemis 2.24.x LWT message send,it cannot invoke before or after Send method > and i just invoke xxxMessageRoute method and i can't get zhe correspond > remoteConnection; > -- > > Key: ARTEMIS-3948 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3948 > Project: ActiveMQ Artemis > Issue Type: Wish > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > > i want develop a plugin to catch zhe LWT message and get zhe correspond > remoteConnection; > after 2.24.x it can't do; > can u expose zhe remoteConnection when route LWT mesage? > if u not do zhis ,it will case connect state not correct; when lwt message > not process in time,and new connect it wil case wrong state > > but apache-activemq-5.16.4 version send LWT message can get remote connect id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3948) artemis 2.24.x LWT message send,it cannot invoke before or after Send method and i just invoke xxxMessageRoute method and i can't get zhe correspond remoteConnection;
[ https://issues.apache.org/jira/browse/ARTEMIS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3948: -- Description: i want develop a plugin to catch zhe LWT message and get zhe correspond remoteConnection; after 2.24.x it can't do; can u expose zhe remoteConnection when route LWT mesage? if u not do zhis ,it will case connect state not correct; when lwt message not process in time,and new connect it wil case wrong state but apache-activemq-5.16.4 version send LWT message can get remote connect id use ProducerBrokerExchange was: i want develop a plugin to catch zhe LWT message and get zhe correspond remoteConnection; after 2.24.x it can't do; can u expose zhe remoteConnection when route LWT mesage? if u not do zhis ,it will case connect state not correct; when lwt message not process in time,and new connect it wil case wrong state but apache-activemq-5.16.4 version send LWT message can get remote connect id > artemis 2.24.x LWT message send,it cannot invoke before or after Send method > and i just invoke xxxMessageRoute method and i can't get zhe correspond > remoteConnection; > -- > > Key: ARTEMIS-3948 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3948 > Project: ActiveMQ Artemis > Issue Type: Wish > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > > i want develop a plugin to catch zhe LWT message and get zhe correspond > remoteConnection; > after 2.24.x it can't do; > can u expose zhe remoteConnection when route LWT mesage? > if u not do zhis ,it will case connect state not correct; when lwt message > not process in time,and new connect it wil case wrong state > > but apache-activemq-5.16.4 version send LWT message can get remote connect id > use > ProducerBrokerExchange -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3948) artemis 2.24.x LWT message send,it cannot invoke before or after Send method and i just invoke xxxMessageRoute method and i can't get zhe correspond remoteConnection;
[ https://issues.apache.org/jira/browse/ARTEMIS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3948: -- Summary: artemis 2.24.x LWT message send,it cannot invoke before or after Send method and i just invoke xxxMessageRoute method and i can't get zhe correspond remoteConnection; (was: artemis 2.24.x will message send,can't get zhe correspond remoteConnection;) > artemis 2.24.x LWT message send,it cannot invoke before or after Send method > and i just invoke xxxMessageRoute method and i can't get zhe correspond > remoteConnection; > -- > > Key: ARTEMIS-3948 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3948 > Project: ActiveMQ Artemis > Issue Type: Wish > Components: ActiveMQ-Artemis-Native >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Assignee: Clebert Suconic >Priority: Major > > i want develop a plugin to catch zhe LWT message and get zhe correspond > remoteConnection; > after 2.24.x it can't do; > can u expose zhe remoteConnection when route LWT mesage? > if u not do zhis ,it will case connect state not correct; when lwt message > not process in time,and new connect it wil case wrong state -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3948) artemis 2.24.x will message send,can't get zhe correspond remoteConnection;
gongping.zhu created ARTEMIS-3948: - Summary: artemis 2.24.x will message send,can't get zhe correspond remoteConnection; Key: ARTEMIS-3948 URL: https://issues.apache.org/jira/browse/ARTEMIS-3948 Project: ActiveMQ Artemis Issue Type: Wish Components: ActiveMQ-Artemis-Native Affects Versions: 2.24.0 Reporter: gongping.zhu Assignee: Clebert Suconic i want develop a plugin to catch zhe LWT message and get zhe correspond remoteConnection; after 2.24.x it can't do; can u expose zhe remoteConnection when route LWT mesage? if u not do zhis ,it will case connect state not correct; when lwt message not process in time,and new connect it wil case wrong state -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578221#comment-17578221 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/11/22 2:46 AM: thx, i have send mail i want receive 133(0x85) when i use a not empty illegal client_id to connect server; was (Author: JIRAUSER293605): i want receive 133(0x85) when i use a not empty illegal client_id to connect server; > 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)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578221#comment-17578221 ] gongping.zhu commented on ARTEMIS-3913: --- i want receive 133(0x85) when i use a not empty illegal client_id to connect server; > 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)
[jira] [Updated] (ARTEMIS-3926) how can join artemis develop and submit code
[ https://issues.apache.org/jira/browse/ARTEMIS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3926: -- Attachment: ClientIdValidateException.java > how can join artemis develop and submit code > > > Key: ARTEMIS-3926 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3926 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ClientIdValidateException.java, MQTTProtocolHandler.java > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3926) how can join artemis develop and submit code
[ https://issues.apache.org/jira/browse/ARTEMIS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3926: -- Attachment: MQTTProtocolHandler.java > how can join artemis develop and submit code > > > Key: ARTEMIS-3926 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3926 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Priority: Major > Attachments: ClientIdValidateException.java, MQTTProtocolHandler.java > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3926) how can join artemis develop and submit code
[ https://issues.apache.org/jira/browse/ARTEMIS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17577128#comment-17577128 ] gongping.zhu edited comment on ARTEMIS-3926 at 8/9/22 4:24 AM: --- i have define ClientIdValidateException runtime exception, and modify MQTTProtocolHandler when device connect server with not null client_id; my ActiveMQSecurityManager5 will validate zhe client_id; and validate zhe client_id is legal or not, when it illigal then throw ClientIdValidateException and return MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID code to zhe client was (Author: JIRAUSER293605): i have define ClientIdValidateException runtime exception, when device connect server with not null client_id; my ActiveMQSecurityManager5 will validate zhe client_id; and when zhe client_id is illigal then throw ClientIdValidateException and return MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID code to zhe client > how can join artemis develop and submit code > > > Key: ARTEMIS-3926 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3926 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3926) how can join artemis develop and submit code
[ https://issues.apache.org/jira/browse/ARTEMIS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17577128#comment-17577128 ] gongping.zhu commented on ARTEMIS-3926: --- i have define ClientIdValidateException runtime exception, when device connect server with not null client_id; my ActiveMQSecurityManager5 will validate zhe client_id; and when zhe client_id is illigal then throw ClientIdValidateException and return MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID code to zhe client > how can join artemis develop and submit code > > > Key: ARTEMIS-3926 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3926 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.24.0 >Reporter: gongping.zhu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3926) how can join artemis develop and submit code
gongping.zhu created ARTEMIS-3926: - Summary: how can join artemis develop and submit code Key: ARTEMIS-3926 URL: https://issues.apache.org/jira/browse/ARTEMIS-3926 Project: ActiveMQ Artemis Issue Type: New Feature Components: Broker Affects Versions: 2.24.0 Reporter: gongping.zhu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/6/22 8:45 AM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, and after it conn success . i Unplug the network cable for test; and zhe server do not call ActiveMQServerMessagePlugin afterSend method; it just call beforeMessageRoute、afterMessageRoute method；and zhe route method cannot get session info [client_id、connId、clientIp；how can i get zhe session info after lastWill sended; why it cannot expose ServerSession paramter for zhe beforeMessageRoute、afterMessageRoute method was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, and after it conn success . i Unplug the network cable for test; and zhe server do not call ActiveMQServerMessagePlugin afterSend method; it just call beforeMessageRoute、afterMessageRoute method；and zhe route method cannot get session info [client_id、connId、clientIp；how can i get zhe session info after lastWill sended; > 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)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 1:50 PM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, and after it conn success . i Unplug the network cable for test; and zhe server do not call ActiveMQServerMessagePlugin afterSend method; it just call beforeMessageRoute、afterMessageRoute method；and zhe route method cannot get session info [client_id、connId、clientIp；how can i get zhe session info after lastWill sended; was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message, and also the ActiveMQServerMessagePlugin method can not invoke > 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)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 9:56 AM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message, and also the ActiveMQServerMessagePlugin method can not invoke was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message > 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)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 9:47 AM: --- i use the MqttAsyncClient to connect the sever and it can not receive the code and i found another problem, i has set the lastWill, after it conn success Unplug the network cable for test; and zhe server can not send zhe lastWill message was (Author: JIRAUSER293605): i use the MqttAsyncClient to connect the sever and it can not receive the code > 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)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575676#comment-17575676 ] gongping.zhu commented on ARTEMIS-3913: --- i use the MqttAsyncClient to connect the sever and it can not receive the code > 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)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575497#comment-17575497 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 12:37 AM: my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; implementation 'org.eclipse.paho:org.eclipse.paho.mqttv5.client:1.2.5' !image-2022-08-05-08-32-12-492.png! was (Author: JIRAUSER293605): my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; !image-2022-08-05-08-32-12-492.png! > 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)
[jira] [Updated] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3913: -- Attachment: image-2022-08-05-08-32-12-492.png > 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)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575497#comment-17575497 ] gongping.zhu commented on ARTEMIS-3913: --- my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; !image-2022-08-05-08-32-12-492.png! > 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)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575021#comment-17575021 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/4/22 5:05 AM: --- thx a lot do mind tell me which version can send 134 reason code to clien after clientId validate fail; and my test verion is apache-artemis-2.23.1, and it just send (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; was (Author: JIRAUSER293605): thx a lot do mind tell me which version can send 134 reason code to clien after clientId validate fail; and the apache-artemis-2.23.1 version just send (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575021#comment-17575021 ] gongping.zhu commented on ARTEMIS-3913: --- thx a lot do mind tell me which version can send 134 reason code to clien after clientId validate fail; and the apache-artemis-2.23.1 version just send (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574971#comment-17574971 ] gongping.zhu commented on ARTEMIS-3913: --- ActiveMQSecurityManager5 authenticate method can not throw ActiveMQSecurityException > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574971#comment-17574971 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/4/22 12:19 AM: ActiveMQSecurityManager5 authenticate method can not throw ActiveMQSecurityException for not RuntimeException was (Author: JIRAUSER293605): ActiveMQSecurityManager5 authenticate method can not throw ActiveMQSecurityException > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574971#comment-17574971 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/4/22 12:19 AM: thx a lot,and ActiveMQSecurityManager5 authenticate method can not throw ActiveMQSecurityException for not RuntimeException was (Author: JIRAUSER293605): ActiveMQSecurityManager5 authenticate method can not throw ActiveMQSecurityException for not RuntimeException > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574112#comment-17574112 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 8:44 AM: --- yes，I want use plugin to auth client ID value,and if validation fails the server disconnect client and response with a specific reason code to client was (Author: JIRAUSER293605): yes，I want use plugin to auth client ID value,and if validation fails the server disconnect client and response with a specific reason code > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574112#comment-17574112 ] gongping.zhu commented on ARTEMIS-3913: --- yes，I want use plugin to auth client ID value,and if validation fails the server disconnect client and response with a specific reason code > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:54 AM:
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
...
}
!image-2022-08-02-08-54-34-267.png!
!image-2022-08-02-08-23-52-965.png!
!image-2022-08-02-08-24-39-288.png!
public class MQTTProtocolHandler extends ChannelInboundHandlerAdapter
{ ... ... }
!image-2022-08-02-08-45-11-459.png!
when i use wireshark capture log
!image-2022-08-02-08-31-01-074.png!
was (Author: JIRAUSER293605):
my ArtemisBorkderPlugin code
{quote}public class ArtemisBrokerPlugin implements ActiveMQServerPlugin,
Serializable {{quote}
{quote}...{quote}
{quote}@Override
public void beforeCreateSession(String name, String username, int
minLargeMessageSize,
RemotingConnection connection, boolean autoCommitSends, boolean autoCommitAcks,
boolean preAcknowledge,
boolean xa, String defaultAddress, SessionCallback callback, boolean
autoCreateQueues, OperationContext context,
Map prefixes) throws ActiveMQException {
if(debug) {
log.info("beforeCreateSession {},{},{},{},{}", connection.getClientID(),
connection.getRemoteAddress(), connection.getID(), name, username);
}
String connId = connection.getID().toString();
if(deviceAuthEnabled && !authConnectTables.containsKey(connId)) {
// Debug.print(log);
authConnectTables.put(connId,0);
doConnectValidation(connection);
}
}{quote}
{quote}private void doConnectValidation(RemotingConnection connection) throws
ActiveMQException{
Boolean success = false;
String error = "";
boolean invalid = false;
int locked = 0;
int eft = 0;
String clientId = connection.getClientID();
String connId = connection.getID().toString();
String clientIp = connection.getRemoteAddress().toString();
clientIp = formatClientIP(clientIp);
try{
/**
* 设备授权校验
*/
boolean invalidClientId = invalidClientId(clientId);
if(invalidClientId){//licId@mac
/**
* 无效的ClientId
*/
invalid = true;
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,非授权设备",clientId));
}
/**
* 连接用户校验
* 有效的ClientId格式
*/
if(!isService(clientId)){
String[] clientIdElements = clientId.split(CLIENT_SPLITOR);
String licId = clientIdElements[0];
String devId = clientIdElements[1];
/**
* 开启设备授权
*/
if(deviceAuthEnabled){
/**
* 新设备
*/
if(!authDeviceTables.containsKey(clientId)){
/**
* 验证设备
*/
DeviceAuth auth = validate(licId,devId);
/**
* 新设备
*/
if(ObjectUtil.isNotEmpty(auth)){
/**
* 设备第一次
*/
if(ObjectUtil.isEmpty(auth.getDevId())){
String lockerSql = deviceAuthLockerSQL;
/**
* 防止一个licId被多台设备使用
*/
locked = deviceJdbcTemplate.update(lockerSql, new Object[]\{devId, licId});
if(locked==0){
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,不能在多台设备上使用",licId));
}
auth.setDevId(devId);
authDeviceTables.put(clientId,auth);
}
}
}
}
/**
* 更新设备状态【连接】
*/
if(deviceStatusSyncabled){
String sql = connectUpdateSQL;
String brokerIp = IPUntil.getLocalIp();
eft = deviceJdbcTemplate.update(sql, new Object[]\{connId,clientIp,
brokerIp,licId});
}
}
success = true;
}
catch(ActiveMQException ex){
error = ex.getMessage();
throw ex;
}
finally{
String prefix = "连接异常";
if(success){
prefix = "连接成功";
log.info("{} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId,locked,eft);
}
else{
if(invalid) {
log.debug("{} {} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId,locked,eft, error);
}
else{
log.info("{} {} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId, locked,eft,error);
}
}
}
}{quote}
{quote}/**
* @param licId yekerId
* @param devId cpusn or mac_address
*/
private DeviceAuth validate(String licId,String devId) throws ActiveMQException
{
/**
* YekerId@CPU_SN;保证一个YekerId只被一台设备使用
*/
String sql = deviceAuthCheckSQL;
List deviceAuths = deviceJdbcTemplate.query(sql, new
Object[]\{licId}, new RowMapperResultSetExtractor(new
BeanPropertyRowMapper(DeviceAuth.class)));
if (deviceAuths == null || ObjectUtil.isEmpty(deviceAuths)) {
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,非授权设备",licId));
}
DeviceAuth auth = deviceAuths.get(0);
if (ObjectUtil.isNotEmpty(auth.getDevId())
&& !auth.getDevId().equalsIgnoreCase(devId)) {
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,不能在多台设备上使用",licId));
}
return auth;
}{quote}
{quote}..{quote}
!image-2022-08-02-08-23-52-965.png!
!image-2022-08-02-08-24-39-288.png!
public class MQTTProtocolHandler extends ChannelInboundHandlerAdapter
{ ... ... }
!image-2022-08-02-08-45-11-459.png!
when i use wireshark capture log
!image-2022-08-02-08-31-01-074.png!
> MQTTReasonCodes byte loss of precision，must int type
>
>
>
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:49 AM:
my ArtemisBorkderPlugin code
{quote}public class ArtemisBrokerPlugin implements ActiveMQServerPlugin,
Serializable {{quote}
{quote}...{quote}
{quote}@Override
public void beforeCreateSession(String name, String username, int
minLargeMessageSize,
RemotingConnection connection, boolean autoCommitSends, boolean autoCommitAcks,
boolean preAcknowledge,
boolean xa, String defaultAddress, SessionCallback callback, boolean
autoCreateQueues, OperationContext context,
Map prefixes) throws ActiveMQException {
if(debug) {
log.info("beforeCreateSession {},{},{},{},{}", connection.getClientID(),
connection.getRemoteAddress(), connection.getID(), name, username);
}
String connId = connection.getID().toString();
if(deviceAuthEnabled && !authConnectTables.containsKey(connId)) {
// Debug.print(log);
authConnectTables.put(connId,0);
doConnectValidation(connection);
}
}{quote}
{quote}private void doConnectValidation(RemotingConnection connection) throws
ActiveMQException{
Boolean success = false;
String error = "";
boolean invalid = false;
int locked = 0;
int eft = 0;
String clientId = connection.getClientID();
String connId = connection.getID().toString();
String clientIp = connection.getRemoteAddress().toString();
clientIp = formatClientIP(clientIp);
try{
/**
* 设备授权校验
*/
boolean invalidClientId = invalidClientId(clientId);
if(invalidClientId){//licId@mac
/**
* 无效的ClientId
*/
invalid = true;
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,非授权设备",clientId));
}
/**
* 连接用户校验
* 有效的ClientId格式
*/
if(!isService(clientId)){
String[] clientIdElements = clientId.split(CLIENT_SPLITOR);
String licId = clientIdElements[0];
String devId = clientIdElements[1];
/**
* 开启设备授权
*/
if(deviceAuthEnabled){
/**
* 新设备
*/
if(!authDeviceTables.containsKey(clientId)){
/**
* 验证设备
*/
DeviceAuth auth = validate(licId,devId);
/**
* 新设备
*/
if(ObjectUtil.isNotEmpty(auth)){
/**
* 设备第一次
*/
if(ObjectUtil.isEmpty(auth.getDevId())){
String lockerSql = deviceAuthLockerSQL;
/**
* 防止一个licId被多台设备使用
*/
locked = deviceJdbcTemplate.update(lockerSql, new Object[]\{devId, licId});
if(locked==0){
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,不能在多台设备上使用",licId));
}
auth.setDevId(devId);
authDeviceTables.put(clientId,auth);
}
}
}
}
/**
* 更新设备状态【连接】
*/
if(deviceStatusSyncabled){
String sql = connectUpdateSQL;
String brokerIp = IPUntil.getLocalIp();
eft = deviceJdbcTemplate.update(sql, new Object[]\{connId,clientIp,
brokerIp,licId});
}
}
success = true;
}
catch(ActiveMQException ex){
error = ex.getMessage();
throw ex;
}
finally{
String prefix = "连接异常";
if(success){
prefix = "连接成功";
log.info("{} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId,locked,eft);
}
else{
if(invalid) {
log.debug("{} {} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId,locked,eft, error);
}
else{
log.info("{} {} {} {} {} {} {}", prefix, formatClientId(clientId),
clientIp,connId, locked,eft,error);
}
}
}
}{quote}
{quote}/**
* @param licId yekerId
* @param devId cpusn or mac_address
*/
private DeviceAuth validate(String licId,String devId) throws ActiveMQException
{
/**
* YekerId@CPU_SN;保证一个YekerId只被一台设备使用
*/
String sql = deviceAuthCheckSQL;
List deviceAuths = deviceJdbcTemplate.query(sql, new
Object[]\{licId}, new RowMapperResultSetExtractor(new
BeanPropertyRowMapper(DeviceAuth.class)));
if (deviceAuths == null || ObjectUtil.isEmpty(deviceAuths)) {
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,非授权设备",licId));
}
DeviceAuth auth = deviceAuths.get(0);
if (ObjectUtil.isNotEmpty(auth.getDevId())
&& !auth.getDevId().equalsIgnoreCase(devId)) {
throw new
MQTTRuntimesException(MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID,String.format("%s,不能在多台设备上使用",licId));
}
return auth;
}{quote}
{quote}..{quote}
!image-2022-08-02-08-23-52-965.png!
!image-2022-08-02-08-24-39-288.png!
public class MQTTProtocolHandler extends ChannelInboundHandlerAdapter
{ ... ... }
!image-2022-08-02-08-45-11-459.png!
when i use wireshark capture log
!image-2022-08-02-08-31-01-074.png!
was (Author: JIRAUSER293605):
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:45 AM:
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled)
{ accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword); }
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled)
{ deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword); }
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:43 AM:
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled)
{ accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword); }
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled)
{ deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword); }
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:42 AM:
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled)
{ accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword); }
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled)
{ deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword); }
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:40 AM:
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled)
{ accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword); }
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled)
{ deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword); }
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu edited comment on ARTEMIS-3913 at 8/2/22 12:33 AM:
my ArtemisBorkderPlugin code
```
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled)
{ accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword); }
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled)
{ deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword); }
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573974#comment-17573974
]
gongping.zhu commented on ARTEMIS-3913:
---
my ArtemisBorkderPlugin code
```
package com.yeker.iot.broker.plugin.impl;
import cn.hutool.core.util.ObjectUtil;
import com.yeker.iot.broker.plugin.impl.model.Account;
import com.yeker.iot.broker.plugin.impl.model.DeviceAuth;
import com.yeker.sdk.comm.util.IPUntil;
import org.apache.activemq.artemis.api.core.*;
import org.apache.activemq.artemis.core.persistence.OperationContext;
import org.apache.activemq.artemis.core.postoffice.RoutingStatus;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTReasonCodes;
import
org.apache.activemq.artemis.core.protocol.mqtt.exceptions.MQTTRuntimesException;
import org.apache.activemq.artemis.core.server.ActiveMQServer;
import org.apache.activemq.artemis.core.server.ServerSession;
import org.apache.activemq.artemis.core.server.plugin.ActiveMQServerPlugin;
import org.apache.activemq.artemis.core.transaction.Transaction;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.protocol.SessionCallback;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.jdbc.core.BeanPropertyRowMapper;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowMapperResultSetExtractor;
import java.io.Serializable;
import java.util.List;
import java.util.Map;
import java.util.concurrent.ConcurrentHashMap;
public class ArtemisBrokerPlugin implements ActiveMQServerPlugin, Serializable {
private Logger log = LoggerFactory.getLogger(ArtemisBrokerPlugin.class);
/**
* 遗言topic前缀
*/
private static final String MISSING_TOPIC_PREFIX = "msg.req.lwt";
/**
* 服务端clientId前缀
*/
private static final String SERVICE_CLIENT_ID_PREFIX = "service-";
/**
* client id 分隔符
*/
private static final String CLIENT_SPLITOR = "@";
/**
* 账号数据库信息
*/
private String accountDriver;
private String accountUrl;
private String accountUsername;
private String accountPassword;
private JdbcTemplate accountJdbcTemplate;
/**
* 授权认证
*/
private boolean accountAuthEnabled = false;
private String accountAuthQuerySQL;
/**
* 设备数据库信息
*/
private String deviceDriver;
private String deviceUrl;
private String deviceUsername;
private String devicePassword;
private JdbcTemplate deviceJdbcTemplate;
/**
* 设备授权
*/
private boolean deviceAuthEnabled = false;
private String deviceAuthCheckSQL;
private String deviceAuthLockerSQL;
private boolean deviceStatusSyncabled = false;
private String connectUpdateSQL;
private String disconnectUpdateSQL;
private String lwtUpdateSQL;
private String resetUpdateSQL;
private Map authConnectTables = new ConcurrentHashMap<>();
private Map authDeviceTables = new ConcurrentHashMap<>();
private boolean debug = false;
@Override
public void init(Map properties) {
this.accountDriver = properties.get("accountDriver");
this.accountUrl = properties.get("accountUrl");
this.accountUsername = properties.get("accountUsername");
this.accountPassword = properties.get("accountPassword");
this.accountAuthEnabled = Boolean.valueOf(properties.get("accountAuthEnabled"));
if(this.accountAuthEnabled){
accountJdbcTemplate =
build(accountDriver,accountUrl,accountUsername,accountPassword);
}
this.accountAuthQuerySQL = properties.get("accountAuthQuerySQL");
this.deviceDriver = properties.get("deviceDriver");
this.deviceUrl = properties.get("deviceUrl");
this.deviceUsername = properties.get("deviceUsername");
this.devicePassword = properties.get("devicePassword");
this.deviceAuthEnabled = Boolean.valueOf(properties.get("deviceAuthEnabled"));
if(this.deviceAuthEnabled){
deviceJdbcTemplate =
build(deviceDriver,deviceUrl,deviceUsername,devicePassword);
}
this.deviceAuthCheckSQL = properties.get("deviceAuthCheckSQL");
this.deviceAuthLockerSQL = properties.get("deviceAuthLockerSQL");
this.deviceStatusSyncabled =
Boolean.valueOf(properties.get("deviceStatusSyncabled"));
this.connectUpdateSQL = properties.get("connectUpdateSQL");
this.disconnectUpdateSQL = properties.get("disconnectUpdateSQL");
this.lwtUpdateSQL = properties.get("lwtUpdateSQL");
this.resetUpdateSQL = properties.get("resetUpdateSQL");
log.info("init ：[{}] ",properties);
log.info("AccountAuthEnabled ：[{}] ", accountAuthEnabled);
log.info("DeviceAuthEnabled ：[{}] ", deviceAuthEnabled);
log.info("DeviceStatusSyncabled ：[{}] ", deviceStatusSyncabled);
log.info("{} 插件初始化",this.getClass().getSimpleName());
}
@Override
public void afterCreateConnection(RemotingConnection connection) throws
ActiveMQException {
if(debug){
log.info("afterCreateConnection
{},{},{}",connection.getClientID(),connection.getRemoteAddress(),connection.getID());
}
}
/**
*
* @param name
* @param username
* @param minLargeMessageSize
* @param connection
* @param
[jira] [Updated] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3913: -- Attachment: image-2022-08-02-08-31-01-074.png > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3913: -- Attachment: image-2022-08-02-08-24-39-288.png > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3913: -- Attachment: image-2022-08-02-08-23-52-965.png > 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 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
gongping.zhu created ARTEMIS-3913: - Summary: 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 Components: ActiveMQ-Artemis-Native Reporter: gongping.zhu Assignee: Clebert Suconic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3912) when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client
gongping.zhu created ARTEMIS-3912: - Summary: when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client Key: ARTEMIS-3912 URL: https://issues.apache.org/jira/browse/ARTEMIS-3912 Project: ActiveMQ Artemis Issue Type: Bug Components: ActiveMQ-Artemis-Native Affects Versions: 2.23.1 Reporter: gongping.zhu Assignee: Clebert Suconic when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3911) when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client
gongping.zhu created ARTEMIS-3911: - Summary: when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client Key: ARTEMIS-3911 URL: https://issues.apache.org/jira/browse/ARTEMIS-3911 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 2.23.1 Reporter: gongping.zhu when develop Artemis pulgin，after client id auth failed ，sever can not response MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID reason to the mqtt client -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3910) Artemis 插件开发时，客户端鉴权失败后，不能返回 MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID
gongping.zhu created ARTEMIS-3910: - Summary: Artemis 插件开发时，客户端鉴权失败后，不能返回 MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID Key: ARTEMIS-3910 URL: https://issues.apache.org/jira/browse/ARTEMIS-3910 Project: ActiveMQ Artemis Issue Type: Bug Components: MQTT Affects Versions: 2.23.1 Reporter: gongping.zhu 插件接口只抛出ActiveMQException，但是 ActiveMQExceptionType有没有定义，无效客户端Id的错误码，同时 MQTTProtocolHandler在执行act的时候，没有区分错误原因，统一返回了断开连接的code给到客户端； 期望在插件验证后直接给到自己想要的错误码给到客户端 -- This message was sent by Atlassian Jira (v8.20.10#820010)
