Cannot Reproduce
Details
Assignee
Michael OffnerMichael OffnerReporter
Adam WinterAdam WinterPriority
CriticalLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Adam Winter
Adam WinterPriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 5 September 2017 at 13:34
Updated 6 December 2018 at 05:54
Resolved 6 December 2018 at 05:54
The attached file is a snippet of the lucee-server.xml file where the configuration seems to have binary data injected in it, thereby corrupting the file and preventing the Lucee service from starting. Seems to be related to the redis sentinel driver. Didn't have a problem with the corruption until we migrated from 5.1.1.30 to 5.2.4.29. Same redis driver.
In addition, I don't believe we had problems until we made some configuration changes to the namespaces represented for the cache objects. Perhaps there's an issue with writing out that portion configuration. The issue lies in the value of the parameter lucee-core-version.