Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: websocket app demo connection cleanup #1576

Open
1 task done
philhosophy opened this issue Dec 24, 2024 · 1 comment
Open
1 task done

[Bug]: websocket app demo connection cleanup #1576

philhosophy opened this issue Dec 24, 2024 · 1 comment

Comments

@philhosophy
Copy link

File Name

gemini/multimodal-live-api/websocket-demo-app/backend/main.py

What happened?

closing connections and cleanup

Relevant log output

websockets.exceptions.ConnectionClosedError: received 1011 (internal error) Request trace id: f102afa6f090070d, [ORIGINAL ERROR] generic::resource_exhausted: RESOURCE_EXHAUSTED: Maximum concurrent se; then sent 1011 (internal error) Request trace id: f102afa6f090070d, [ORIGINAL ERROR] generic::resource_exhausted: RESOURCE_EXHAUSTED: Maximum concurrent se

Code of Conduct

  • I agree to follow this project's Code of Conduct
@rajeevrj256
Copy link

Your WebSocket server ran out of resources due to too many connections or insufficient system capacity. The error RESOURCE_EXHAUSTED means the maximum allowed concurrent connections were reached, causing the server to close connections with an internal error.

Fix it by:

Increasing server resource limits.
Closing idle or unused WebSocket connections.
Adding load balancing for high traffic.
Debugging connection cleanup in your backend code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants