As I encountered problem with the coldfusion-out.log rotation process I tried to change the value of the parameters maxOutFileBackup and maxOutLogSize in the neo-logging.xml file and restart the coldfusion service. The new parameters are not systematically taken into account and I could have coldfusion-out.log bigger than the max size defined in the xml file. Content of the deployed neo-logging.xml: <wddxPacket version='1.0'><header/><data><array length='2'><array length='0'></array><struct type='coldfusion.server.ConfigMap'><var name='consoleVisible'><boolean value='false'/></var><var name='maxFileSize'><number>7.05032E8</number></var><var name='enableOSLogging'><boolean value='false'/></var><var name='maxOutFileBackup'><number>20.0</number></var><var name='pattern'><string>"%p","%t",%d{"MM/dd/yy","HH:mm:ss"},"%a","%m%x"%n</string></var><var name='maxOutLogSize'><number>20.0</number></var><var name='maxFileBackup'><number>10.0</number></var><var name='consolePattern'><string>%d{MMM d, yyyy HH:mm:ss a} %p [%t] - %m%n</string></var><var name='priority'><string>information</string></var><var name='logDirectory'><string>E:\Logs\ColdFusion</string></var></struct></array></data></wddxPacket> On my platform, 3 similar servers are deployed and on one of the three (despite of the updated info in neo-logging.xml file) I still have coldfusion-out.log not rotated wih big size (more than 7gb). Any ideas to try to understand why the behavior is not reliable ?
... View more