History

Zaiming (Stone) Shi e73bf716ae fix(emqx_channel): do not log stale sock_close event as error In some cases, EMQX may decide to close socket and mark connection at 'disconnected' state, for example, when DISCONNECTE packet is received, or, when failed to write data to socket. However, by the time EMQX decided to close the socket, the socket might have already been closed by peer, and the `tcp_closed` envet is already delivered to the process mailbox -- causing EMQX to handle sock_close event at 'disconnected' state.		2023-11-19 22:27:25 +01:00
..
include	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
src	fix(emqx_channel): do not log stale sock_close event as error	2023-11-19 22:27:25 +01:00
test	fix(Stomp): content type returned	2023-11-02 11:21:27 +00:00
.gitignore	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
README.md	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
rebar.config	refactor: move emqx_json to emqx_utils_json	2023-04-14 13:31:27 +02:00

README.md

emqx_stomp

The Stomp Gateway is based on the Stomp v1.2 and is compatible with the Stomp v1.0 and v1.1 specification.

Quick Start

In EMQX 5.0, Stomp gateway can be configured and enabled through the Dashboard.

It can also be enabled via the HTTP API or emqx.conf, e.g. In emqx.conf:

gateway.stomp {

  mountpoint = "stomp/"

  listeners.tcp.default {
    bind = 61613
    acceptors = 16
    max_connections = 1024000
    max_conn_rate = 1000
  }
}

Note: Configuring the gateway via emqx.conf requires changes on a per-node basis, but configuring it via Dashboard or the HTTP API will take effect across the cluster.