2 Correct answers
I know the indexing was functioning correctly prior to the update. I have an application that compares directory files to indexed files daily. Missing indexed files generate a ticket in our ticketing system for my review. This ticket was generated the day after the update installation.
By @keith_6356
From your description of when the error occurred and from researching the POI namespace error online, I think it is caused by the library xmlbeans-5.3.0.jar. Update 15 introduced this new XmlB
...
Keith, please now try to see if that remaining problem goes away with stopping cf, deleting the felix-cache folder (in cfusion/bin), then restarting cf.
54
Replies
I know the indexing was functioning correctly prior to the update. I have an application that compares directory files to indexed files daily. Missing indexed files generate a ticket in our ticketing system for my review. This ticket was generated the day after the update installation.
By @keith_6356
From your description of when the error occurred and from researching the POI namespace error online, I think it is caused by the library xmlbeans-5.3.0.jar. Update 15 introduced this new XmlBean library. The version in Update 14 and Update 13 is xmlbeans-3.1.0.jar.
So I assume that the error does not occur with xmlbeans-3.1.0.jar. But your installation may now be using xmlbeans-5.3.0.jar instead. It would have been imported when you installed Update 15, but remained in your installation when you reverted to Update 13 or 14. This idea is the basis for a workaround.
Possible workaround:
- Open the ColdFusion Administrator and go to the page Package Manager > Packages > Installed Packages.
- Click on the search package. You should then see the settings for the Search package. Confirm that xmlbeans-5.3.0.jar is in the Required Jars list. Our idea is that that is the cause of the problem.
- In the Available Versions dropdown, select the previous version and click on the Downgrade button. Click on OK to accept the change.
- Return to the page Installed Packages. You will see a red flag, symbolizing the downgraded package. Click once again on the search package. You should now see xmlbeans-3.1.0.jar in the Required Jars list.
- Restart ColdFusion.
- Test to see whether cfindex works as before.
Folks, I've found the solution. And bkbk I don't expect what you've proposed will work, but what I have to propose will.
By @Charlie Arehart
Charlie, it's great news that you have found a solution and I look forward to hearing about it. However, why do you say, in advance, that my suggestion won't work?
I have just tested what I suggested. It works.
I am on ColdFusion 2025 Update 3. As you yourself have confirmed it has the issue the issue reported by @keithm99725152 :
Cannot resolve type for handle _XY_Q=space|R=
My test runs as follows.
- I put a DOCX file, a PDF file and a TXT file in a directory. I placed the file indexTest.cfm in the same directory. It contains the code:
<cfset collectionName = "myCollection">
<cfset targetDirectory = expandPath("indexFiles")>
<!--- Index the files --->
<cfindex
collection="#collectionName#"
action="update"
type="path"
key="#targetDirectory#"
extensions=".pdf,.doc,.docx,.txt"
recurse="YES">
<!--- Output result --->
<cfoutput>
Indexed files from #targetDirectory# into collection "#collectionName#".
</cfoutput>
2. When I launched indexTest.cfm, I could see the following Warnings in coldfusion-out.log:
Aug 16, 2025 10:31:20 AM Warning [http-nio-8500-exec-3] - WARNING: Could not index C:\ColdFusion2025\cfusion\wwwroot\workspace\CF_Project\indexFiles\myWord.docx in SOLR. Check the exception for more details: Cannot resolve type for handle _XY_Q=space|R=space@http://www.w3.org/XML/1998/namespace (org.apache.poi.schemas.ooxml.system.ooxml.cttext7f5btype) - code 13
Aug 16, 2025 10:31:20 AM Warning [http-nio-8500-exec-3] - WARNING: Could not index C:\ColdFusion2025\cfusion\wwwroot\workspace\CF_Project\indexFiles\myWord.docx in SOLR. Check the exception for more details: Content of file myWord.docx can not be extracted.
3. I downgraded the search package, following the steps in the workaround that I proposed.
4. When I launched indexTest.cfm and looked at coldfusion-out.log, there were no longer any Warnings.
That said, I realize that there have been problems with POI libraries in recent ColdFusion updates. Like you, I too am looking into the issue. For example, I have found the following.
Until Update 14 of ColdFusion 2023 the highest POI version used was poi-4.1.2.jar, of which one of the dependencies is xmlbeans-3.1.0. In Update 15 of last July, the POI version was upgraded to poi-5.4.1.jar, with dependency xmlbeans-5.3.0.jar. However, there might be problems of backward-compatibility in the move from xmlbeans-.3.1.0.jar to xmlbeans-5.3.0.jar.
If your application manipulates DOCX (XWPF), XLSX (XSSF/SXSSF) or PPTX (XSLF) with Apache POI, the jump from xmlbeans 3.1.0 to xmlbeans 5.3.0 (curent release used in POI 5.4.1) can bite in the following ways:
-
Difference in generated classes / schemas: POI ships pre-generated OOXML (.docx, xlsx, pptx) schema bindings (ooxml-schemas / poi-ooxml-full). These are regenerated against the newer xmlbeans 5.3.0 runtime. As a result, your code may experience stricter XML validation. Some documents that loaded error-free in 3.1.0 may now throw a warning. Some documents that loaded with warnings in 3.1.0 may now throw exceptions. The difference in generated schemas may also create differences in whitespace or namespace handling. That is because xmlbeans parsing got stricter in 5.3.0. For example, XML that previously ignored unexpected attributes may now fail to load.
-
Possible package relocation and dependency conflicts: the groupId/artifactId for xmlbeans changed in the 5.x line (org.apache.xmlbeans:xmlbeans), while older 3.x versions sometimes appeared under different coordinates. If your application or its dependencies still bring 3.x jars, you can hit ClassCastException or LinkageError at runtime. To avoid this, you must ensure only one xmlbeans version is on the classpath (5.3.0). I am therefore alerted when I see xmlbeans-3.1.0.jar and mlbeans-5.3.0.jar together in C:\ColdFusion2023\bundles\repo.
I am still looking into the subject. I shall of course share any new information that I find.
@keithm99725152 , for your information:
- I have just done the 6 steps of the workaround on ColdFusion 2023 Update 15. I downgraded the search package from version 2023.0.15.330825 to version 2023.0.11.330706.
 
- The ColdFusion build before the workaround (2023.0.15.330825) remains the same after the workaround.
@BKBK this work around worked in test just fine, when I implameted it in production I'm getting this error 'void org.apache.xmlbeans.XmlOptions.put(java.lang.Object)' null
I do not understand because they are identical with the exception test is 2023 is developers editions and production is 2023 standard.
AdChoices