Error! The remote party closed the WebSocket connection without completing the close handshake.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, unity
- Domain
- game-dev, mobile-dev, networking
Research direction
The report identifies only the websocket example, with no file, test, or entry point to inspect. Reproduce the close-handshake failure under the stated iOS, Android, Unity, and high-message-rate conditions, then establish and verify a concrete fix or configuration change that keeps affected clients connected.
Written by the indexing model from the issue text.
Description
Hello,
I am using your code "websocket example" and i have issue it is happen in (IOS , Android ,Unity editor ) when i send 5000 messages per sec from every 4 devices i have this problem
Error! The remote party closed the WebSocket connection without completing the close handshake..
Why i do that "send 5000 message" from every mobile ? because i have game already published and there is active users between 3000 to 40000 daily and a make more test to understand why this problem i have it! because every day i have this problem and users can't play, maybe 300 to 600 can play!
In your opinion, how can I solve this problem?
More information:
Server : 32 Core / 30 GB Memory - from Google cloud .
Protocol type : TCP
Storage : 60 SSD
And thank you for plugin is very helpful.
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from endel/NativeWebSocket
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
endel/NativeWebSocket#107 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
endel/NativeWebSocket#102 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
endel/NativeWebSocket#101 · 6 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
endel/NativeWebSocket#95 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
endel/NativeWebSocket#94 · 2 comments ·
All issues in endel/NativeWebSocket
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·