Details
-
Bug
-
Resolution: Fixed
-
High
-
Known Issues 5.x Stack, 5.1, 5.2
-
None
Description
Since it relies on forks, the asynchronous publishing daemon always resets active database connections as soon as a fork is done, in order to avoir errors such as "MySQL has gone away".
It isn't done for the PDO links provided by the new stack to clear persistence cache, leading to a fatal when a publishing child tries to clear persistence cache.
Attachments
Issue Links
- discovered while testing
-
EZP-21913 Hotfix usage of global in cli scripts
- Closed