Cfindex not indexing .docx word documents files

[keith_6356]

On Thursday, the error below began appearing after the last 2023 coldfusion update on my cfindex code that is atleast 10 years old. I found removing the .dot file extension from my extensions list stopped the error from occurring. However, .docx files will not index now.

I tried to uninstall the update 15, although this did not solve the error or the indexing issue 

Message

com.zaxxer.sparsebits.SparseBitSet not found by poi-5.4.1 [36]

StackTrace

java.lang.ClassNotFoundException: com.zaxxer.sparsebits.SparseBitSet not found by poi-5.4.1 [36] at org.apache.poi.xslf.usermodel.XSLFSheet.<init>(XSLFSheet.java:89) at org.apache.poi.xslf.usermodel.XSLFSlideMaster.<init>(XSLFSlideMaster.java:64) at org.apache.poi.ooxml.POIXMLFactory.createDocumentPart(POIXMLFactory.java:61) at org.apache.poi.ooxml.POIXMLDocumentPart.read(POIXMLDocumentPart.java:671) at org.apache.poi.ooxml.POIXMLDocument.load(POIXMLDocument.java:165) at org.apache.poi.xslf.usermodel.XMLSlideShow.<init>(XMLSlideShow.java:126) at coldfusion.tagext.search.MSDocument.readPPTX(MSDocument.java:206) at coldfusion.tagext.search.SolrUtils.getSolrDocument(SolrUtils.java:817) at coldfusion.tagext.search.SolrUtils.addDocument(SolrUtils.java:1439) at coldfusion.tagext.search.IndexTag.doUpdate(IndexTag.java:683) at coldfusion.tagext.search.IndexTag.doStartTag(IndexTag.java:352) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:5083) at cffile_index_intranet2ecfm1052529286.runPage(D:\tasks\file_index_intranet.cfm:38) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:251) at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:749) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:578) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:613) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:162) at coldfusion.filter.IpFilter.invoke(IpFilter.java:45) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:97) at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:81) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:231) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:46) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:762) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:447) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:935) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1826) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1189) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:658) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) at java.base/java.lang.Thread.run(Thread.java:833)

[keithm99725152]

That worked, thank you @Charlie Arehart & @BKBK for all your help

[BKBK]

@keithm99725152 ,  thank you too for the collaboration.

[Charlie Arehart]

Very good to hear. Thanks for the update. 

So to be clear, was this still cfindex processing that now failed after the July cf update? (You could have been doing processing with the cf spreadsheet tag or functions.)

I ask this for the sake of others who might find this, and also to update that bug report I'd created (and mentioned here) last week:

https://tracker.adobe.com/#/view/CF-4227542

(Update, 50 mins after I asked. I found your previous reply to BKBK where you DID clarify it was cfindex processing that now failed with xlsx files. Sorry, I was working on my phone for my previous replies today: a little more challenging. Anyway, I will go ahead and add that clarification to the bug report.)

[BKBK]

@keithm99725152 ,

Thanks for the update. I am glad to hear that the workaround works for docx. 

As Charlie's research shows, your xlsx file (and other POI applications) fail for exactly the same reason. And as he has shown, the workaround is the same: downgrading the relevant package(s) to the last version.

[Charlie Arehart]

To help those who may find this thread (such as if searching brings them here), I want to offer a summary. There was the initial problem reported, then others discovered. It's a very long thread.

• First, what Keith reported originally was that as of the July 2025 CF updates (in his case, of cf2023), his use of cfindex would no longer work for .docx files
• He also reported that uninstalling that July update did NOT resolve the problem
• For the first couple of days we pursued a couple of lines of consideration, including whether it may be due to an error in the update process
• But I later confirmed not only that I could recreate the problem, but that it was true also for those on CF2025 and CF2021 who applied the July Update. I also filed an Adobe bug report
• BKBK then proposed downgrading the search package, which proved to solve the problem of .docx files not being indexed
• But Keith later reported that he now found also .xlsx files would not index
• I proposed he downgrade the spreadsheet package. He reported at first that didn't work, but then I reminded him to clear the felix-cache, and then he reported now it worked:  he could now use cfindex to process .docx and .xlsx files, along with the others that had been working

While that takes care of his cfindex problems (and it would work for those who apply the July update and then uninstall it), it still didn't explain why uninstalling the July update left things in this seemingly broken state.

And for that I had (in the midst of all the dozens of replies) also identified and reported here a different problem that expands WELL BEYOND this one matter of cfindex.  Indeed, it can explain many, many problems that some (not all) people have had with recent updates and unusual package management problems.  It has to do with what I've documented is a seeming misconfiguration in the bundlesdependency.json file which is downloaded from Adobe when one performs a CF update (or CF package updates).  For now, check out that message I just linked to. I will eventually create a new bug report (at tracker.adobe.com).

For now, I have updated that other bug report (about this cfindex problem) to also summarize both the workarounds and note this new, different (but related) problem.  So while Keith's original problem seems resolved, for now, this really is just the start of a new journey related to this other issue. I think we will want to create a new thread on that, and let this one close. Maybe I'll do that after I create the Adobe bug report. I'll also do a blog post, as that new info seems important news to share well beyond this one forum thread on cfindex.

But I hope this summary of things helps put a nice bow on this one, for now. If I missed or forgot anything, let me know.