Alvaro, you may be interested in testing out 
https://github.com/apache/solr/pull/4853.

It is both a upgrade to Tika 4, which may be an issue for you as it’s a big 
change, but also I think some improvements in thread safety.

Specifically when I did the upgrade with Claude help, it spotted: 
https://github.com/apache/solr/pull/4853/changes#diff-6af572cef0d99c0806e2160f62988c25226df77a7976495a5b1323796ddcf1c0

You could probably take this PR, and just take the SaxParser changes and have 
that in its own PR with the existing Tika 3 that shipped in Solr 10.    If you 
do make a PR for that, please tag me, happy to get it merged.

Eric



> On Sep 21, 2026, at 12:20 PM, Alvaro Lechner <[email protected]> wrote:
> 
> I am using Solr 9.6 in an application with more than 10M documents indexed. 
> Around 50% of them are PDF or office documents that need extraction. Whenever 
> I need to reindex (for example, when upgrading the Solr version), I usually 
> start 5 parallel processes, which works fine.
> 
> Now, while testing Solr 10 in containers and configured to use TikaServer 
> (running in a separate container), I found that as soon as I start a second 
> indexing process, Solr throws errors like this:
> 
> 2026-09-21 15:35:49.117 ERROR (qtp1917025677-36-null-745) [ x:documents 
> t:null-745] o.a.s.s.HttpSolrCall 500 Exception 
> =>org.apache.solr.common.SolrException: org.xml.sax.SAXException: FWK005 
> parse may not be called while parsing. at 
> org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:202)
> 
> Gemini suggested that this issue is caused by the reuse of a SAXParser. 
> Following that, I tried looking into the source code with GitHub Copilot, and 
> it suggested a fix by modifying TikaServerParser.java.
> 
> I would appreciate it if someone could validate this behavior and provide a 
> fix in upcoming versions.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast, a leader in email security and cyber 
resilience. Mimecast integrates email defenses with brand protection, security 
awareness training, web security, compliance and other essential capabilities. 
Mimecast helps protect large and small organizations from malicious activity, 
human error and technology failure; and to lead the movement toward building a 
more resilient world. To find out more, visit our website.

Reply via email to