Bug 51520 - XSSFFormulaEvaluator fails if formula references row above 65536
Summary: XSSFFormulaEvaluator fails if formula references row above 65536
Status: RESOLVED WORKSFORME
Alias: None
Product: POI
Classification: Unclassified
Component: XSSF (show other bugs)
Version: 3.8-dev
Hardware: PC All
: P2 major (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-17 16:29 UTC by Gabe Roffman
Modified: 2013-08-05 12:16 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gabe Roffman 2011-07-17 16:29:22 UTC 
Within an .xslx file with a formula in a cell that references a row greater than 65536, the XSSFFormulaEvaluator returns "Unknown error type: -60".
 Within a cell, I have a formula of "=SUM(A3:A70000)".  This will work if I make the range below the 65536 mark.  However, with it above, I get the following stack trace:


java.lang.IllegalArgumentException: Unknown error type: -60
	at org.apache.poi.ss.usermodel.FormulaError.forInt(FormulaError.java:131)
	at org.apache.poi.xssf.usermodel.XSSFCell.setCellErrorValue(XSSFCell.java:667)
	at org.apache.poi.xssf.usermodel.XSSFFormulaEvaluator.setCellValue(XSSFFormulaEvaluator.java:209)
	at org.apache.poi.xssf.usermodel.XSSFFormulaEvaluator.evaluateFormulaCell(XSSFFormulaEvaluator.java:153)
	at org.apache.poi.hssf.usermodel.HSSFFormulaEvaluator.evaluateAllFormulaCells(HSSFFormulaEvaluator.java:327)
	at org.apache.poi.hssf.usermodel.HSSFFormulaEvaluator.evaluateAllFormulaCells(HSSFFormulaEvaluator.java:318)
	at org.apache.poi.xssf.usermodel.XSSFFormulaEvaluator.evaluateAllFormulaCells(XSSFFormulaEvaluator.java:238)
Comment 1 Nick Burch 2011-07-17 17:41:09 UTC 
Have you tried with a recently nightly build? Only there was something similar (bug #51448 IIRC) which was fixed, and that may solve this issue too
Comment 2 Dominik Stadler 2013-08-05 12:16:06 UTC 
no response in a long time => resolving for now, please reopen with more information if this is still an issue