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

Timeouts despite the configuration is set according to the recommendation #62

Open
c-schinzer opened this issue Jun 30, 2022 · 4 comments

Comments

@c-schinzer
Copy link

Hi,

strangely enough I still see timeouts when configuring as per recommendation. When analyzing the related Server Error I do not see any trace of Facile in it, while I think I should, the stack trace only refers to the AbstractMySQLDriver, Doctrine/DBAL/Driver/PDOMySql/Driver, Doctrine/DBAL/Connection.

How can I check that the configured Driver and Connection class are really loaded?
When running the bin/console debug:container command, I can see this

...
  doctrine.dbal.connection                                                                         Doctrine\DBAL\Connection                                                                        
  doctrine.dbal.connection.configuration                                                           Doctrine\DBAL\Configuration                                                                     
  doctrine.dbal.connection.event_manager                                                           Symfony\Bridge\Doctrine\ContainerAwareEventManager                                              
  doctrine.dbal.connection_factory                                                                 Doctrine\Bundle\DoctrineBundle\ConnectionFactory                                                
  doctrine.dbal.default_connection                                                                 Facile\DoctrineMySQLComeBack\Doctrine\DBAL\Connection                                           
  doctrine.dbal.default_connection.configuration                                                   Doctrine\DBAL\Configuration                                                                     
  doctrine.dbal.default_connection.event_manager                                                   Symfony\Bridge\Doctrine\ContainerAwareEventManager                                              ...

Should it look like that?
Thanks for having a look.

Warm regards

Carsten

@c-schinzer
Copy link
Author

Just for completeness, the config file:

doctrine:
    dbal:
        connections:
            default:
                url: '%env(resolve:DATABASE_URL)%'
                driver_class: 'Facile\DoctrineMySQLComeBack\Doctrine\DBAL\Driver\PDOMySql\Driver'
                server_version: 'mariadb-10.1.40'
                wrapper_class: 'Facile\DoctrineMySQLComeBack\Doctrine\DBAL\Connection'
                options:
                    x_reconnect_attempts: 5

@Jean85
Copy link
Member

Jean85 commented Jul 1, 2022

Can you post the stack trace of the issue?
Which versions of the packages are you using?
Are you sure that you're not in one of the cases where we can't intervene due to idempotence, like for an update query?

@c-schinzer
Copy link
Author

c-schinzer commented Jul 1, 2022

I attach the PDF of the Symfony Error Page.
My composer.lock is fixed upon:

        "doctrine/annotations": "^1.0", // 1.13.2
        "doctrine/doctrine-bundle": "^2.1", //2.3.2
        "doctrine/doctrine-migrations-bundle": "^2.2.0", // 2.2.3
        "doctrine/orm": "^2.6", // 2.7.5
        "facile-it/doctrine-mysql-come-back": "^1.8", // 1.8

I am am observing this in DRYRUN mode, i.e. the only real DB transactions are SELECTs.
An exception occurred in driver_ SQLSTATE[HY000] [2002] Connection timed out (500 Internal Server Error).pdf

@Jean85
Copy link
Member

Jean85 commented Apr 1, 2023

Sorry for not getting back at you.
Did you solve the issue? Did you check that your configuration was correctly applied to your environment? Did you try bin/console debug:config doctrine to do it?

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