[
https://issues.apache.org/jira/browse/TIKA-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528136#comment-17528136
]
Hudson commented on TIKA-3734:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #186 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/186/])
TIKA-3734 -- fix new junrar IllegalArgumentException on streams of zero length.
(tallison:
[https://github.com/apache/tika/commit/f218c99bc41df0aa6d420595ba27cf3418298040])
* (edit) tika-parsers/src/main/java/org/apache/tika/parser/pkg/RarParser.java
TIKA-3734 -- fix new junrar IllegalArgumentException on streams of zero length
-- force recording of zero byte issue and extracted metadata (tallison:
[https://github.com/apache/tika/commit/d97935028bbba7d830d61bf445d9fb2bf9b029be])
* (edit) tika-parsers/src/main/java/org/apache/tika/parser/pkg/RarParser.java
> Upgraded junrar parser throwing IllegalArgumentException on zero-byte streams
> -----------------------------------------------------------------------------
>
> Key: TIKA-3734
> URL: https://issues.apache.org/jira/browse/TIKA-3734
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 1.28.2, 2.4.0
>
>
> There's a new exception in junrar parsers. When the junrar parser hits a
> stream that is zero bytes, it now throws an IllegalArgumentException. That
> percolates through our stack and the rest of the file is not parsed.
> We should add a check to see from the header if the unpackaged size is > 0.
> The triggering file:
> {color:#067d17}DXXPDWQF6LURIMASV5I2PRQTTWXBTAW2{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
