Details
Assignee
Michael OffnerMichael OffnerReporter
Nick KwiatkowskiNick KwiatkowskiPriority
NewNew 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
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Nick Kwiatkowski
Nick KwiatkowskiPriority
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
Created 25 June 2023 at 23:37
Updated 28 November 2024 at 15:23
On initial startup, two ORM logs are created (expected). Locations at :
/opt/lucee/server/lucee-server/context/logs/orm.log /opt/lucee/web/logs/orm.log
However, these files are never updated. When using the following directive in the application.cfc :
this.ormsettings = { logsql: true};
the expectation is that one of the above log files be populated with SQL debugging statements and the statements that were executed against the DB. There are references in the docs that log4j settings would need to be updated, but it is very difficult to inject these into stateful containers.
Normal practice would be to soft-link these files to /dev/stdout in order to capture these logs to the docker/k8 console.