Closed sonalranjit closed 10 months ago
Hi @sonalranjit, thank you for writing in.
Have you experienced the same issue in a different network setting, such as on your local machine? If not, this problem may be specific to the infra where you're running the app. We've never received this type of error report in the last few years since this project started. Therefore, I'm wondering if there might be a specific reason causing the situation you're experiencing.
Additionally, if switching from JavaWebsocket to the default option can resolve the issue, it could be related to the underlying WebSocket client library.
@seratch It's difficult to reproduce this on a local machine because, we only encounter this when the application runs for a long period of time. It happens randomly, for months it will have no issues and then suddenly an event like this would occur. Our infra team notice just the connection resets.
I can switch the backend websocket client library to the tyrus standalone and give it a try.
👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.
Switching to tyrus websocket client, we haven't encountered the issue so far the app has been running stably since the switch last over last month.
Our slack application periodically spams the channels it is in with repeated retries of commands it has been issued. Further inspection on logs shows it is repeatedly creating new sessions forever until the application is restarted manually and a stable websocket connection is formed.
Reproducible in:
The Slack SDK version
Java Runtime version
OS info
Steps to reproduce:
Expected result:
The application should gracefully handle connection resets from Slack's API and recreate and maintain a stable websocket connection.
Actual result:
The application repeatedly creates new sessions:
Further inspection of the network traffic in our environment shows the connection being severed from Slack's API after a payload of 3MB is sent from the slack server side.
Is there any mitigation for scenarios like this ? It's causing the application to spam the channels it is in perhaps because the connection is being severed continually and the slack's api is retrying and the case here is new sessions are being created as well repeatedly so the retries go on and on.