Tony, I have a potential solution, an explanation, the steps to take, and an offer of more help if it's not that.
1) With a classnotfound exception like that, arising unexpectedly--and especially when you feel you do nothing with the said java object in your code, my first guess would be that this is an impact of a) having the "save class files" enabled on the cf admin caching page (a good thing, set on by default) and b) then doing either of two things: a cf update (as you've indicated, though these rarely cause this problem) or a change of Java from one major version to another.
And in either case, a simple solution is to clear the cfclasses folder for the cf instance, in its wwwroot/WEB-INF/cfclasses (NOT the sibling classes).
2) This is needed in such cases because the cfml for a given template was compiled in the past using a given Java version (which now fails) , and if it were recompiled with the new Java it would work. Again, this can also happen (though rarely with some cf updates, like the Elvis operator problem that hit many with the march cf updates).
And as for the fact that it sometimes happens and sometimes does not, it could withe be due to really being different templates (indicated in the error), or due to the flow of control in the template only sometimes hitting the line of cfml code that has this problem (or perhaps with different values for the attributes of a cf tag or args to a cf function at that line of code).
3) So Tony, can you first confirm if an instance in question has "save class files" enabled? If so, turning it off is NOT the answer. You'd stop each instance, clear that cfclasses folder (or rename it, and cf will create it anew on restart).
Yes, it means that after CF restarts, each template requested will be compiled, but that cost is generally negligible--paid only one time since the option to save the class files is enabled. (That's one more reason that turning it off is NOT the answer. The other is that if there are classes in cfclasses, cf may load those regardless of that setting.)
Try this on even one instance if you may prefer, to see if that instance alone no longer exhibits the problem.
Let us know how it goes. If it doesn't solve things, there can be any number of other things that are NOT necessarily a bug. (That said, I'd think it a mistake/wrong for your bug to be closed without any explanation, and I'd press for that regardless, if I were you.)
4) Finally, as to what it may be, if it's not this and not a bug, I will say I suspect I could help you assess and perhaps find an explanation, in less than an hour, in a remote scteenshare consulting session. I help people that way daily, and have often solved even such knotty inexplicable problems. If you don't find the time to be valuable, you'd not pay for it. More at the consulting page at carehart.org. Just offering that as a last resort.
Hope the other info above may get you going.
/Charlie (troubleshooter, carehart. org)
22
Replies
AdChoices