Skip to content

Tags: cloudamqp/amqproxy

Tags

v2.0.3

[v2.0.3] - 2024-10-23

- Added config option term_client_close_timeout and cli option --term-client-close-timeout to set how long to wait for clients to close their connections before sending Close when amqproxy receives a TERM signal.
- Added a HTTP health check on http://listen_address:http_port/healthz
- Added metrics on http://listen_address:http_port/metrics
- Don't log when a client just opens and closes a TCP connection
- Compile static binary

v2.0.2

Verified

This commit was signed with the committer’s verified signature.
spuun Jon Börjesson
version bump

v2.0.1

v2.0.1

- Return unused memory faster to the OS using GC_UNMAP_THRESHOLD=1 in Dockerfile and systemd service file
- Compile with Crystal 1.13.0, fixes a potential memory leak in Log

v2.0.0

v2.0.0

- IPv6 addresses in brackets supported in upstream URL (eg. amqp://[::1])
- Otherwise unchanged from v2.0.0-rc.8
- Main difference against v1.x is that channels are pooled, multiple client channels are shared on a single upstream connection, dramatically decreasing the number of upstream connections needed

v2.0.0-rc.8

v2.0.0-rc.8

- Allow large client frame sizes, but split body frames to client if smaller than upstream frame size, to support large Header frames

v2.0.0-rc.7

v2.0.0-rc.7

- Send all GetOk response frames in one TCP packet

v2.0.0-rc.6

v2.0.0-rc.6

- Bugfix: Send Connection.Close-ok to client before closing TCP socket
- Bugfix: Pass Channel.Close-ok down to client

v2.0.0-rc.5

v2.0.0-rc.5

- Bugfix: negotiate frame_max 4096 for downstream clients

v2.0.0-rc.4

v2.0.0-rc.4 - 2024-04-11

- Bufix: Only send channel.close once, and gracefully wait for closeok
- Buffer publish frames and only send full publishes as RabbitMQ doesn't support channel.close in the middle of a publish frame sequence
- Optimization: only flush socket buffer after a full publish sequence, not for each frame