[
https://issues.apache.org/jira/browse/TIKA-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leszek Sliwko updated TIKA-4385:
--------------------------------
Description:
As per
[https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/Process.html:]
_Because some native platforms only provide limited buffer size for standard
input and output streams, failure to promptly write the input stream or read
the output stream of the process may cause the process to block, or even
deadlock._
The fix is to read the output buffer in another thread. Sample file causing
this issue attached.
was:
As per
[https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/Process.html:]
_Because some native platforms only provide limited buffer size for standard
input and output streams, failure to promptly write the input stream or read
the output stream of the process may cause the process to block, or even
deadlock._
The fix is to read the output buffer in another thread.
> GDALParser deadlocks while reading gdalinfo output
> --------------------------------------------------
>
> Key: TIKA-4385
> URL: https://issues.apache.org/jira/browse/TIKA-4385
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 3.1.0
> Reporter: Leszek Sliwko
> Priority: Minor
> Attachments: content-type-test.grb2
>
>
> As per
> [https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/Process.html:]
> _Because some native platforms only provide limited buffer size for standard
> input and output streams, failure to promptly write the input stream or read
> the output stream of the process may cause the process to block, or even
> deadlock._
> The fix is to read the output buffer in another thread. Sample file causing
> this issue attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
