org.apache.tika.exception.TikaException

Failed to communicate with a forked parser process. The process has most likely crashed due to some error like running out of memory. A new process will be started for the next parsing request.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web46

  • via tika-user by Clemens Wyss DEV, 9 months ago
    Failed to communicate with a forked parser process. The process has most likely crashed due to some error like running out of memory. A new process will be started for the next parsing request.
  • via Stack Overflow by Alex Kleshchevnikov
    , 1 year ago
    Failed to communicate with a forked parser process. The process has most likely crashed due to some error like running out of memory. A new process will be started for the next parsing request.
  • via tika-user by Heck, Gus (Patrick), 9 months ago
    Failed to communicate with a forked parser process. The process has most likely crashed due to some error like running out of memory. A new process will be started for the next parsing request.
  • Stack trace

    • org.apache.tika.exception.TikaException: Failed to communicate with a forked parser process. The process has most likely crashed due to some error like running out of memory. A new process will be started for the next parsing request. at org.apache.tika.fork.ForkParser.parse(ForkParser.java:120) at org.apache.tika.fork.ForkParserTest$1.run(ForkParserTest.java:80) Caused by: java.io.IOException: The pipe has been ended at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.DataOutputStream.flush(DataOutputStream.java:106) at org.apache.tika.fork.ClassLoaderResource.process(ClassLoaderResource.java:65) at org.apache.tika.fork.ForkClient.waitForResponse(ForkClient.java:174) at org.apache.tika.fork.ForkClient.sendObject(ForkClient.java:137) at org.apache.tika.fork.ForkClient.call(ForkClient.java:108) at org.apache.tika.fork.ForkParser.parse(ForkParser.java:117) ... 1 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    8 times, 2 weeks ago
    Once, 2 months ago
    Once, 2 months ago
    Once, 3 months ago
    35 more bugmates