dpol1 opened a new pull request, #3022: URL: https://github.com/apache/tika/pull/3022
tika-grpc shared one single-threaded PipesClient across all handler threads, so concurrent fetchAndParse calls corrupted the IPC and crashed the worker. This routes them through the existing PipesParser pool: numClients is honored, and saturation surfaces in-band as CLIENT_UNAVAILABLE_WITHIN_MS to keep the v1 status-in-reply model. The second commit closes the connection when an in-flight process() is interrupted, so a pooled client can't go back to the queue dirty. Details and repro: [TIKA-4815](https://issues.apache.org/jira/browse/TIKA-4815). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
