Ok, very weird one. Last night we go some unexpected errors. The errors were all caused by Lucee (or the Java) reporting the wrong timestamp. In our code, Lucee saw the timestamp as being from Jan 1, 1900. What's really weird is all the logs that were written show the correct timestamp, so the problem seems to be somewhere within the application code. This is code that has not changed in a long time and we've never seen this behavior before. Now it's possible this was an issue within our VM host and it was sporadically returning the wrong clock values, but given that none of our logs have the incorrect timestamps, I'm thinking the issue was either with our code (or some weird issue within Lucee or Java). All our code is doing is storing the now() (although the millisecond precision is rounded down to match SQL Server's datetime data type). This has all worked flawlessly for years. This is under Lucee 5.4.3.2 and Java 11.0.23. Has anyone ever seen anything like this before?