-
Close Search
Newbie
Server.log filling up with message “http://apache.org/xml/features/disallow-doctype-decl”
Since migrating to CF 2025, our server.log has recorded entries like this everytime we run a cfindex with action update:
“Error”,”ajp-nio-127.0.0.1-8024-exec-26″,”07/26/26″,”03:40:19″,””,”http://apache.org/xml/features/disallow-doctype-decl”
These are simple collections populated by queries, and the number of log entries are far greater than the number of collection items. For example, our daily re-index of several collections totalling <10K items generates over 40K log entries. Despite these errors, the collections are updating.
Neither the debugging nor exception.log entries (redacted sample below) are pointing us to solutions. This issue has persisted through Updates 9-11. Is anyone else experiencing this problem?
Since migrating to CF 2025, our server.log has recorded entries like this everytime we run a cfindex with action update:
“Error”,”ajp-nio-127.0.0.1-8024-exec-26″,”07/26/26″,”03:40:19″,””,”http://apache.org/xml/features/disallow-doctype-decl”
These are simple collections populated by queries, and the number of log entries are far greater than the number of collection items. For example, our daily re-index of several collections totalling <10K items generates over 40K log entries. Despite these errors, the collections are updating.
Neither the debugging nor exception.log entries (redacted sample below) are pointing us to solutions. This issue has persisted through Updates 9-11. Is anyone else experiencing this problem?
You must be logged in to post a comment.
- Most Recent
- Most Relevant
Pete, while it’s of course frustrating to experience such an error, solving it sometimes takes detective work. I suspect you’ve searched for references and found none. And since you say the problem remains in updates 9-11 (and perhaps 12,which came out yesterday), it seems you’re regarding this as a bug that you hoped some cf update would eventually fix.
But let’s consider it instead as something being the result of a change introduced by some update. As you may know, most cf updates address security concerns, and some remove functionality (sacrificing compatibility for security), while at the same time offering a jvm arg that can be added to cf to reverse that changed behavior (sacrificing security for compatibility).
Indeed, multiple updates to cf2025 and cf2023 have done that. There is a page for each of those listing them:
But in reviewing that list, none may be obvious (none are said to affect cfindex, but several relate to xml–as your error refers to).
In that case, surmising which arg may affect you depends on knowing when this cfindex behavior last worked for you. So when it did, were you on cf2023? 2021? And either way, what update level? Some changes “happening when moving to cf2025” would have happened “in cf2023”–but only if you’d kept it updated. People often work on servers where no one was keeping cf updated.
So for example (and perhaps this will be a workaround for you), update 3 of cf2025 (and update 15 of cf2023) introduced a change that could result in the error you see, though it’s not so obvious that it would. (I discussed it in my blog post on the update last year.)
Can you try adding:
-Dcoldfusion.xml.allowExternalEntities=true
to the end of your java.args line in the jvm.config file in your cf instance (likely in coldfusion2025/cfusion/bin. Save off a copy of the file before changing it). And don’t add this as a new line, but at the end of all values on that java.args line, with a space separating it from others. Save the file (keeping it open), then restart cf.
If cf won’t start, you made some mistake in adding that arg (thus my two warnings, and also why I proposed you keep the file open). Worst case, recover using the file copy you’d made.
Does that fix it? If so, that’s “good news”, that the error stops. But again you’ve removed a protection Adobe had added for your good. Am I saying leave it at this? No. The point here is that if you confirm this fixes it, you can also dig into what xml is at issue…whether something you’re processing or that Cf itself (or the solr engine underlying cfindex) may be.
And at least if it’s the latter, you or Adobe can dig into what that’s about, that was sensitive to this change. And yes, maybe they will then see it as a bug to be fixed.
I know this ws a lot to read. You likely just want a solution, not a sermon or theories. Again, we can’t KNOW this will fix things. That’s why I’d asked when things last worked for you. And I shared the rest to help you or others here in narrowing down the problem and solution.
Please let us know if you try this.
