RocketChat / RocketChat/Rocket.Chat

Snap server install, same message duplicities Realtime API

Open
#27,211 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Hello,

I have an issue using Realtime API when installing Rocket server with Snap and connecting to WebSocket endpoint wss://[ABC.DOMAIN.COM]/websocket of the server it sends duplicates of the same message and even some old messages that have been already sent before. For example, I am listening for private messages of some user and i am getting the same message with the same ID two times when user is posting the message.

When manually installing the server on Ubuntu, Realtime API works as expected only one message is sent to the socket.

Did someone face the issue?

Steps to reproduce:
  1. Install rocket chat server thru Snap
  2. Connect to Websocket API listen all events
  3. Send any event and print messages that are received on socket end
Expected behavior:

1 message = 1 record, receiving two with same ID but slightly different timestamp

Actual behavior:
Server Setup Information:
  • Version of Rocket.Chat Server: Output of snap list: rocketchat-server 3.18.7 1521 3.x/stable rocketchat✓ -
  • Operating System: Ubuntu 20.4
  • Deployment Method: snap
  • Number of Running Instances: 1
Client Setup Information
  • Desktop App or Browser Version: Chrome 106.0.5249.119 (Official Build) (64-bit)
  • Operating System: Windows

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the duplicate WebSocket messages with Rocket.Chat Server 3.18.7 installed through Snap on Ubuntu 20.4, following the listed listener and send-event steps. Compare the received message IDs and timestamps with a manual Ubuntu installation; done means the Snap deployment delivers one record per sent message without old messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.