Project

General

Profile

Actions

Bug #21119

open

Workbench stops receiving websocket messages after a few minutes

Added by Peter Amstutz about 1 year ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Story points:
-

Description

Observed on user cluster:

After a few minutes (~15 minutes the first time I observed this, 4 minutes the second time, the third time it went for 39 minutes) Workbench stops receiving messages from websockets. In the web developer tools, I see a steady stream of messages, which then abruptly comes to a halt.

Unlike the previous websockets bug, upon reconnecting I start receiving messages again.

Message volume here is pretty high, something like 30 messages per second. Each message is 400-600 bytes. These are mostly container updates.

Actions #1

Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)
  • Subject changed from Websockets stops sending messages after 15 minutes to Workbench stops receiving websocket messages after a few minutes
Actions #2

Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz about 1 year ago

  • Target version changed from Development 2023-11-08 sprint to Development 2023-11-29 sprint
Actions #4

Updated by Peter Amstutz about 1 year ago

Next time this is observed -- send SIGABRT to the websockets process and get the stack/thread dump.

Actions #5

Updated by Peter Amstutz about 1 year ago

  • Target version changed from Development 2023-11-29 sprint to Development 2024-01-03 sprint
Actions #6

Updated by Peter Amstutz about 1 year ago

  • Target version changed from Development 2024-01-03 sprint to Development 2024-01-17 sprint
Actions #7

Updated by Peter Amstutz about 1 year ago

  • Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
Actions #8

Updated by Peter Amstutz 11 months ago

  • Target version changed from Development 2024-01-31 sprint to Development 2024-02-14 sprint
Actions #9

Updated by Peter Amstutz 11 months ago

  • Target version changed from Development 2024-02-14 sprint to Development 2024-02-28 sprint
Actions #10

Updated by Peter Amstutz 10 months ago

  • Target version changed from Development 2024-02-28 sprint to To be scheduled
Actions #11

Updated by Peter Amstutz 10 months ago

  • Target version changed from To be scheduled to Future
Actions

Also available in: Atom PDF