-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
BUGFIX: Use dedicated connection for EventStore #5005
Conversation
Yes i observed that already once in ci ... locally it works without ... probably because stuff (schema) is already warmed up? |
@mhsdesign The error is
I guess this is only implicitly related. I'll check again once #4988 is merged |
grml, this isn't solved wiht #4988 it seems – I applied the fix there and checks still fail. ../../bin/behat -f progress --strict --no-interaction '-vvv' '--stop-on-failure' '-c' 'Neos.Neos/Tests/Behavior/behat.yml' =>
So this is the line that fails. I'll investigate.. |
in order to prevent nested transactions potentially leading to RuntimeException of A transaction is active already, can't commit events!
I can confirm that the last version works in conjunction with the reworked catchup: If we were to create a dedicated connection per projection, it would probably work here as well – and maybe that even makes sense since they have their independent transaction boundaries |
I have encountered the bug also in the NodeTemplates Ci (see Flowpack/Flowpack.NodeTemplates@f37b6c4) The first error is: Neos.ContentRepository.Core/Classes/EventStore/EventPersister.php:47 RuntimeException: A transaction is active already, can't commit events! and succeeding errors: Neos.ContentRepository.Core/Classes/Infrastructure/DbalCheckpointStorage.php:88 RuntimeException: Failed to acquire checkpoint lock for subscriber "Neos\ContentRepository\Core\Projection\ContentStream\ContentStreamProjection" because a transaction is active already |
This will hopefully be resolved with #4988 once and for all |
Use a dedicated DBAL Connection for the
DoctrineEventStore
in order to prevent nested transactions potentially leading to RuntimeException ofAs a result, the
doctrine:migrate
andcr:setup
commands can be skipped during CI