Good point! I have thought about that and will try that Monday and see what the results are.
Side note — I will say our FR instance has exception tracing disabled (e.g.
-Dfr.jvmti.enable.exceptions=false) as my testing show it decreased performance by 60%, which I believe prevents the “event snapshot” feature from doing anything.
I don’t want to restart Tomcat right now to test this theory, because I’m trying to run these load tests over several days to try and confirm for @micstriit that the memory leak issue with the class loaders has been resolved.
Fortunately, it’s seems pretty easy to recreate the logs. I just need to run my unit test suite under very heavy application load.
I’ve sort of alluded to, I’m not sure there’s really a problem with the application workflow, other than the excessive log generation. It seems like Lucee is technically working as excepted (outside of the RAM drive issue I also reported), but at bare minimum it certainly should not be writing these exceptions as ERROR level logging. If this is “by design”, it should probably logging these as DEBUG or TRACE log entries, so it doesn’t show up by default and only renders in the logs when you need more thorough logging.
Something else worth noting, these exceptions do not show up in the exception.log, only the application.log.