The interactive file manager requires Javascript. Please enable it or use sftp or scp.
You may still browse the files here.

Name	Modified	Size	InfoDownloads / Week
Parent folder
EMQX Enterprise e5.0.2-alpha.2.tar.gz	2023-03-17	2.3 MB	0
EMQX Enterprise e5.0.2-alpha.2.zip	2023-03-17	3.2 MB	0
README.md	2023-03-17	8.9 kB	0
Totals: 3 Items		5.5 MB	0

e5.0.2-alpha.1 .. e5.0.2-alpha.2

Enhancements

#9893 When connecting with the flag clean_start=false, EMQX will filter out messages that published by banned clients. Previously, the messages sent by banned clients may still be delivered to subscribers in this scenario.
#9564 Implemented Kafka Consumer bridge. Now it's possible to consume messages from Kafka and publish them to MQTT topics.

Bug Fixes

#10117 Fix an error occurring when a joining node doesn't have plugins that are installed on other nodes in the cluster. After this change, the joining node will copy all the necessary plugins from other nodes.
#10130 Fix garbled config display in dashboard when the value is originally from environment variables. For example, env EMQX_STATSD__SERVER='127.0.0.1:8124' . /bin/emqx start results in unreadable string (not '127.0.0.1:8124') displayed in Dashboard's Statsd settings page. Related PR: HOCON#234.
#10144 Add -setcookie emulator flag when invoking emqx ctl to prevent problems with emqx cli when home directory is read only. Fixes #10142

e5.0.1 .. e5.0.2-alpha.2

Enhancements

#10022 Start releasing Rocky Linux 9 (compatible with Enterprise Linux 9) and MacOS 12 packages
#9893 When connecting with the flag clean_start=false, EMQX will filter out messages that published by banned clients. Previously, the messages sent by banned clients may still be delivered to subscribers in this scenario.
#9986 For helm charts, add MQTT ingress bridge; and removed stale mgmt references.
#10083 Add DynamoDB support for Data-Brdige.
#9564 Implemented Kafka Consumer bridge. Now it's possible to consume messages from Kafka and publish them to MQTT topics.
#9881 In this pull request, we have enhanced the error logs related to InfluxDB connectivity health checks. Previously, if InfluxDB failed to pass the health checks using the specified parameters, the only message provided was "timed out waiting for it to become healthy". With the updated implementation, the error message will be displayed in both the logs and the dashboard, enabling easier identification and resolution of the issue.
#9998 Redact the HTTP request body in the authentication error logs for security reasons.

Bug Fixes

#10013 Fix return type structure for error case in API schema for /gateways/:name/clients.
#10014 In dashboard API for /monitor(_current)/nodes/:node return 404 instead of 400 if node does not exist.
#10027 Allow setting node name from EMQX_NODE__NAME when running in docker. Prior to this fix, only EMQX_NODE_NAME is allowed.
#10050 Ensure Bridge API returns 404 status code consistently for resources that don't exist.
#10052 Improve daemon mode startup failure logs.

Before this change, it was difficult for users to understand the reason for EMQX 'start' command failed to boot the node. The only information they received was that the node did not start within the expected time frame, and they were instructed to boot the node with 'console' command in the hope of obtaining some logs. However, the node might actually be running, which could cause 'console' mode to fail for a different reason.

With this new change, when daemon mode fails to boot, a diagnosis is issued. Here are the possible scenarios:

If the node cannot be found from ps -ef, the user is instructed to find information in log files erlang.log.*.
If the node is found to be running but not responding to pings, the user is advised to check if the host name is resolvable and reachable.
If the node is responding to pings, but the EMQX app is not running, it is likely a bug. In this case, the user is advised to report a Github issue.
#10055 Fix mqtt.max_awaiting_rel change does not work.
#10056 Fix /bridges API status code.
Return 400 instead of 403 in case of removing a data bridge that is dependent on an active rule.
Return 400 instead of 403 in case of calling operations (start|stop|restart) when Data-Bridging is not enabled.
#10066 Improve error messages for /briges_probe and [/node/:node]/bridges/:id/:operation API calls to make them more readable. And set HTTP status code to 400 instead of 500.
#10074 Check if type in PUT /authorization/sources/:type matches type given in body of request.
#10079 Fix description of shared_subscription_strategy.
#10085 Consistently return 404 for all requests on non existent source in /authorization/sources/:source[/*].
#10098 A crash with an error in the log file that happened when the MongoDB authorization module queried the database has been fixed.
#10100 Fix channel crash for slow clients with enhanced authentication. Previously, when the client was using enhanced authentication, but the Auth message was sent slowly or the Auth message was lost, the client process would crash.
#10107 For operations on bridges API if bridge-id is unknown we now return 404 instead of 400. Also a bug was fixed that caused a crash if that was a node operation. Additionally we now also check if the given bridge is enabled when doing the cluster operation start . Affected endpoints:
[cluster] /bridges/:id/:operation,
[node] /nodes/:node/bridges/:id/:operation, where operation is one of [start|stop|restart]. Moreover, for a node operation, EMQX checks if node name is in our cluster and return 404 instead of 501.
#10117 Fix an error occurring when a joining node doesn't have plugins that are installed on other nodes in the cluster. After this change, the joining node will copy all the necessary plugins from other nodes.
#10118 Fix problems related to manual joining of EMQX replicant nodes to the cluster. Previously, after manually executing joining and then leaving the cluster, the replicant node can only run normally after restarting the node after joining the cluster again.

Mria PR

#10119 Fix crash when statsd.server is set to an empty string.
#10124 The default heartbeat period for MongoDB has been increased to reduce the risk of too excessive logging to the MongoDB log file.
#10130 Fix garbled config display in dashboard when the value is originally from environment variables. For example, env EMQX_STATSD__SERVER='127.0.0.1:8124' . /bin/emqx start results in unreadable string (not '127.0.0.1:8124') displayed in Dashboard's Statsd settings page. Related PR: HOCON#234.
#10132 Fix systemctl stop emqx command not stopping jq, os_mon application properly, generating some error logs.
#10144 Add -setcookie emulator flag when invoking emqx ctl to prevent problems with emqx cli when home directory is read only. Fixes #10142
#10095 Stop MySQL client from bombarding server repeatedly with unnecessary PREPARE queries on every batch, trashing the server and exhausting its internal limits. This was happening when the MySQL bridge was in the batch mode.