But we don't need to see a comparison of the dump when things fail vs when you add tostring to get it to work. We need to see the dump of the manager variable when the data causes the split to fail vs when the data lets it work.   And please don't use the text format but the traditional html one, with the extra info that may convey regarding the contents of that object. Feel free to take a screenshot of the dumps.  ... View more

the developer told me that the syntax was correct - that he was filtering or limiting the results returned. Before posting, I was looked up the syntax myself and from the Google, it should have been working - but how it goes I act like a court jester and look for answers and it inspires others to do me up ... View more

Thanks for the update, mack. It will be intesesting if others with the error see the same cause. (It confirms this was indeed a page-specific error, as I was asserting in my original reply in June above.) ... View more

Ok on the latter. Bummer on the former. Assuming all is indeed as it should be, I'm out of ideas. Perhaps others here (or Adobe) may offer more. (See also the tracker ticket related to the matter, where a bit more discussion has ensued in comments, after the fix was released.)  ... View more

To be clear, the jetty folder is about the cf add-on service (not monitoring), which is the solr or pdfg/cfhtmltopdf feature.   There are no documented mitigation steps. One could uninstall the cf add-on service if you're not using it. One could even just yank the log4j jar, if you wanted to just stop the add-on service without installing it.    We can hope that some future update (perhaps coming even this month) will address this more appropriately.    BTW, Ripley, the jetty aspect related to monitoring is yet ANOTHER jetty that Cf has had, starting back in cf9, which was about offering a separate port and web server through which to access the enterprise server monitor. It has its own jetty.xml config file in the cfusion/lib folder, which relies on a jetty jar in that folder. That is NOT the cfusion/jetty folder, added starting in cf11 (if one enabled the add-on service at cf install), which is the focus of the log4j concern in this thread. It can get confusing!    Hope that's helpful.  ... View more

hey guys, thanks for the input -  in the application in question is extremely old - probably over 10 years worth of coding - and the cf error handler defiantly looks to be a custom page - we found the the link in one of the class files and it was removed -  and like Eddie said we checked waybackmachine that day after about two hours looking for the string and we came to the same conclusion, we are in process of updating the sites CF version and authentication methods and such. ... View more