-
Notifications
You must be signed in to change notification settings - Fork 480
Closed
Description
Problem Statement
It looks like we are not using socket.io anymore and rolled our own websocket impl. It looks like there is an error in our websocket logic that does not try to reconnect if the socket errors out.
Steps to Reproduce
Not sure - but losing our websockets is part of the issue with the host control.
Acceptance Criteria
The websocket should always work.
dotCMS Version
25.04
Proposed Objective
Application Performance
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Metadata
Metadata
Assignees
Type
Projects
Status
Done