On several occasions, most recently over the last two days, I ran into a problem where Hibernate appears to be holding onto incorrect configuration information even through a CF restart. I have found other posts about people running into similar problems but have yet to see any word from Adobe on this incredibly frustrating problem. Here's how it showed up for me:
As I said, it was all flakey -- it came and went somewhat randomly but if I left out the properties that were not used and hadn't been used for weeks, it showed up. Put them in and it worked fine.
I searched the CF install directory for possible generated config files. I deleted everything in cfcclasses.
Having read that someone else had a similar problem that was solved by creating a new site and newly installing the app,
I did the same and it worked fine -- starts with no problem and ormReload() works as it should.
The point is that Hibernate appears to be writing some record somewhere that survives CF restart which I haven't found documented anywhere.
Could Adobe please identify what the hell is retained between CF start/stops because this was 5 or more hours of time utterly wasted on this project. I ran into a similar thing on an earlier project that due to the same kind of flakiness in which some config seemed to survive CF restart and threw errors I couldn't get rid of with any amount of changes to the CFCs, I had to abandon using Hibernate all together.