You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "chen (Jira)" <ji...@apache.org> on 2021/09/14 11:24:00 UTC

[jira] [Commented] (COMPRESS-589) 1.21 throws a 'java.io.IOException: Truncated TAR archive' exception while 1.20 not

    [ https://issues.apache.org/jira/browse/COMPRESS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414884#comment-17414884 ] 

chen commented on COMPRESS-589:
-------------------------------

[~ggregory] 

figure out that it will throw excption when the .tar file is about 2GB, and little less than 2GB, everything OK, but little bigger than 2GB, the excption throwed.

thats weird and maybe the file is too hard to upload

> 1.21 throws a 'java.io.IOException: Truncated TAR archive' exception while 1.20 not
> -----------------------------------------------------------------------------------
>
>                 Key: COMPRESS-589
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-589
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.21
>            Reporter: chen
>            Priority: Major
>
> the bug happens when I use the TarArchiveInputStream to read bytes from the current tar archive entry.
> the trace shows as below
> {code:java}
> 08-27 14:39:18.657 10633 10963 W System.err: java.io.IOException: Truncated TAR archive
> 08-27 14:39:18.657 10633 10963 W System.err: java.io.IOException: Truncated TAR archive
> 08-27 14:39:18.657 10633 10963 W System.err: at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getActuallySkipped(TarArchiveInputStream.java:478)
> 08-27 14:39:18.657 10633 10963 W System.err: at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.skipRecordPadding(TarArchiveInputStream.java:455)
> 08-27 14:39:18.657 10633 10963 W System.err: at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextTarEntry(TarArchiveInputStream.java:367)
> {code}
> but when i downgrade to 1.20, the exception will not show again, so I think it is a bug in the new version 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)