BUGFIX: Prevent premature connection to database in PersistenceManager::persistAllowedObjects
#3489
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For every simple GET request
persistAllowedObjectsis called via the Package.php in flow. This results in building a db connection, even if there is nothing to do.We first check if the
entityManageris open and if the entity manager has not been used (something is heavily cached via middle-ware or sth) flows objectmanagement retrieves the entity manger.Now in this retrieval process - even though doctrines connection is lazy itself - the connection will be made forcefully see
\Neos\Flow\Persistence\Doctrine\EntityManagerFactory::createline 120 (flow-development-collection/Neos.Flow/Classes/Persistence/Doctrine/EntityManagerFactory.php
Line 120 in 11e2348
flow-development-collection/Neos.Flow/Classes/Persistence/Doctrine/EntityManagerConfiguration.php
Line 229 in d93b6b0
This is ironic because if there is no connection - or no entity manager in the first place, the current process cannot have made any changes to the transaction.
Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX!!!and have upgrade-instructions