[
https://issues.apache.org/jira/browse/TIKA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Filippov reopened TIKA-709:
-----------------------------------
I see you included the fix in some version, and I have one more comment -
you've included the fix just into pipe mode, but it's better to also use
CloseShieldInputStream in server mode. I'll attach a patch with next comment.
> Tika network server does not print anything in response to, for example, Word
> documents
> ---------------------------------------------------------------------------------------
>
> Key: TIKA-709
> URL: https://issues.apache.org/jira/browse/TIKA-709
> Project: Tika
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.9
> Environment: Debian Linux Sid
> Reporter: Vitaliy Filippov
> Assignee: Jukka Zitting
> Fix For: 0.10
>
> Attachments: tika-709.diff
>
>
> When trying to use Tika Server (java -jar tika-app-0.9.jar -t -p PORT) to
> parse M$Word DOC/DOCX files, tika server reads the file and then doesn't do
> anything more, it simply hangs, probably blocked on a socket read. This does
> not happend with, for example, HTML documents. I don't know the mechanics of
> this bug, but the following change definitely fixes the issue:
> Change
> type.process(socket.getInputStream(), output);
> to
> type.process(new CloseShieldInputStream(socket.getInputStream()), output);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
