commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Pavlin (Created) (JIRA)" <>
Subject [jira] [Created] (COMPRESS-174) BZip2CompressorInputStream doesn't handle being given a wrong-format compressed file
Date Wed, 01 Feb 2012 04:08:58 GMT
BZip2CompressorInputStream doesn't handle being given a wrong-format compressed file

                 Key: COMPRESS-174
             Project: Commons Compress
          Issue Type: Bug
          Components: Compressors
    Affects Versions: 1.3
         Environment: Linux and Windows
            Reporter: Andrew Pavlin
            Priority: Minor

When reading a file through BZip2CompressorInputStream, and the user selects a file of the
wrong type (such as ZIP or GZIP), the read blows up with a strange ArrayIndexOutOfBoundException,
instead of reporting immediately that the input data is of the wrong format.

The Bzip2Compressor should be able to identify whether a stream is of BZip2 format or not,
and immediately reject it with a meaningful exception (example: "ProtocolException: not a
BZip2 compressed file").

Alternatively, are there functions in commons-compress that can identify the compression type
of an InputStream by inspection?

Example stack trace when using a ZIP input file:

Exception in thread "OSM Decompressor" java.lang.ArrayIndexOutOfBoundsException: 900000 
        at org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.getAndMoveToFrontDecode(

        at org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.initBlock(

        at org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.setupNoRandPartA(

        at org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.setupNoRandPartB(

        at org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.read0(


        at org.ka2ddo.yaac.osm.OsmXmlSegmenter$ 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message