Closed (fixed)
Project:
Domain
Version:
3.x-dev
Component:
- Domain Config
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Oct 2025 at 21:17 UTC
Updated:
12 Nov 2025 at 10:29 UTC
Jump to comment: Most recent
Comments
Comment #2
mably commentedComment #3
mably commentedComment #5
mably commentedThe implemented solution that fixed the problem was to remove the
ACTIVE_DOMAIN_SETfrom thegetSubscribedEvents()method and rather calladdListenerfor the same event in theDomainConfigFactoryOverrideconstructor.Looks like some very early call to domain negotiation was generating the
ACTIVE_DOMAIN_SETevent that was causing Drupal to instantiate the config overrider service, as it is a subscriber for that event, but as the service was already being loaded/initialized, it caused a fatal loop.Sadly, I haven't been able to reproduce the problem since then.
I you have any idea of what could be the root cause of this problem, feel free to share.
Comment #6
mably commentedPosting another stack trace I was getting where we can see that the
DomainConfigFactoryOverrideservice is looping on itself:Most likely, an
ACTIVE_DOMAIN_SETevent is trying to instantiate the service while it is already being initialized.Comment #7
mably commentedComment #8
mably commentedThis circular dependency error indicates the
ACTIVE_DOMAIN_SETevent is firing while the config overrider factory is still initializing. As a result, the service may never receive that event, preventing it from functioning as intended.A more robust approach would be to remove the event subscription mechanism altogether and rely instead on a dedicated domain negotiation context service.
Created a new issue to work on that: #3554949: Use a domain negotiation context service instead of an event subscriber in config services
Any feedback will be greatly appreciated.
Comment #9
mably commentedComment #11
mably commented