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

Websocket flooding database : PDO // ERROR #451

Open
ma-gu-16 opened this issue Oct 28, 2021 · 1 comment
Open

Websocket flooding database : PDO // ERROR #451

ma-gu-16 opened this issue Oct 28, 2021 · 1 comment

Comments

@ma-gu-16
Copy link

Hi there,

i received the following Error:

request.CRITICAL: Uncaught PHP Exception PDOException: "SQLSTATE[70100]: <<Unknown error>>: 1907 Query execution was interrupted, query_timeout exceeded" at /var/www/vendor/symfony/http-foundation/Session/Storage/Handler/PdoSessionHandler.php line 337 {"exception":"[object] (PDOException(code: 70100): SQLSTATE[70100]: <<Unknown error>>: 1907 Query execution was interrupted, query_timeout exceeded at /var/www/vendor/symfony/http-foundation/Session/Storage/Handler/PdoSessionHandler.php:337)"}

i already increased the timeout, but seems like this is not the problem.
as i figured out my database entries getting bigger and bigger. i safe the symfony user sessions in there.

since i use the authentificated websocket user, i have this problems.

sometimes the the websocket connections doesnt work at first try, because it took to long time i guess to find the right session.

atm the symfony user session db has 1333 entries. i guess thats way to much. should someone remove this entries by time?
i think the websocket makes everytime a new session.

i hope i explained enough and someone can help me.

services.yaml:


  Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler:
    arguments:
      - '%env(DATABASE_URL)%'
      - { db_table: 'symfony_user_session', lock_mode: 0 }

thank you

@mbabker
Copy link
Contributor

mbabker commented Oct 28, 2021

What’s the full stack trace on this error? The fact it is logged on the “request” channel makes me think that the error isn’t even coming from the websocket server (I can’t think of too many services off the top of my head that have the “request” channel logger AND get used in the context of a console command).

The websocket system does not write any session data, it is a 100% read-only interface.

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