使用POI的XSSFWorkBook读.xlsx遇Zip错误，求.xlsx转.csv解决方案

Hey there! Let's walk through concrete, actionable steps to diagnose and fix that confusing exception you're encountering when using Apache POI's XSSFWorkbook for your XLSX-to-CSV conversion.

Key Troubleshooting Steps #

• Verify your XLSX file is valid first
  Sometimes the issue isn't with your code at all—your input file might be corrupted, saved in a non-standard format (e.g., a .xls file renamed to .xlsx), or incomplete (like a partially downloaded file). Try opening it manually in Excel; if Excel throws an error, that's your root cause right there.

• Ensure all Apache POI dependencies are version-aligned
  Mismatched POI component versions are a super common source of weird, unexplained exceptions. If you're using poi-ooxml, make sure poi, poi-ooxml-schemas, and xmlbeans (or poi-ooxml-lite for newer POI versions) all share the exact same version. For example, if you're on POI 5.2.5, every related dependency should be 5.2.5. Check your Maven pom.xml or Gradle build.gradle to confirm this.

• Use the correct XSSFWorkbook constructor for your input source
  You mentioned trying String/Zip-based constructors without luck—let's clarify the right usage based on how you're accessing the file:

  • For local files, wrap the file in a FileInputStream (and always use try-with-resources to auto-close streams):

    try (FileInputStream inputStream = new FileInputStream(new File("path/to/your/file.xlsx"));
         XSSFWorkbook workbook = new XSSFWorkbook(inputStream)) {
        // Your conversion logic here
    } catch (IOException e) {
        // Log the full stack trace here!
        e.printStackTrace();
    }
    

  • Avoid the String constructor unless you're loading a resource from your classpath (not a local file path)—that's probably why it wasn't working for you.

• Capture and analyze the full exception stack trace
  "Ununderstandable exceptions" almost always have clues in their full stack traces. Is it an InvalidFormatException (wrong file type)? An IOException (file not found, permission issues)? Or an OutOfMemoryError (file is too large for in-memory processing)? Printing the entire stack trace will tell you exactly where things are breaking.

• Switch to SXSSFWorkbook for large files
  If your XLSX file is huge, XSSFWorkbook (which loads the entire file into memory) can cause out-of-memory errors. SXSSFWorkbook is POI's streaming alternative—it flushes data to disk as it processes, keeping memory usage low. The API is nearly identical to XSSF, so it's an easy swap for large-file scenarios.

• Isolate the conversion logic
  Sometimes the exception happens not during workbook initialization, but when you're reading cells or formatting CSV output. Simplify your code: comment out the CSV conversion part, just initialize the workbook and iterate through sheets/rows. If that works, the problem is in how you're handling cell data (e.g., formula cells, merged cells, special characters like commas/newlines that break CSV formatting).

内容的提问来源于stack exchange，提问作者mehdmehd