It isn’t case senstitive - AND - it only happened after the upgrade.
So the server settings and source code remain unchanged.
I am, not sure what to put it down to - as I can no longer replicate it, either - after manually inserting an ormReload() into the onApplicationStart() event handler.
And from a trtoubleshooting perspective - can’t repliucate it after removing the ormReload(), either. ;(
It is great, indeed, that it is no longer happening… But weird “shit” like this (no config / code changes) - effecting a previously sound application - behaving differently after a server restart or an upgrade… then not being able to duplicate it - once you get it fixed - seems to be happening fairly often in the dicscussion here.
And just "kicking the tyres, here…
Perhaps there is room for a “start from scratch” process of:
Clean-out everything from caches / class files / etc.
AND “Forcibly” Recreate “everything” as if it never, ever existed option?
I imagine this would be run as part of a “service” (server) start / restart?
(thus inherently used after upgrades)