Bug 47454 - reading excell with autofilter error
Summary: reading excell with autofilter error
Status: RESOLVED FIXED
Alias: None
Product: POI
Classification: Unclassified
Component: HSSF (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-30 02:48 UTC by joao1
Modified: 2010-08-10 14:22 UTC (History)
1 user (show)


Attachments
Trintech_POI examples.zip (874.19 KB, application/x-zip-compressed)
2010-03-26 21:13 UTC, dave.sprague 		Details
View All 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 joao1 2009-06-30 02:48:27 UTC 
There are exceptions thrown when trying to read excel file with autofilter turned on. I've tried various versions of POI jar 2.5.1-3.5
 
java.lang.reflect.InvocationTargetException

and

org.apache.poi.hssf.record.RecordFormatException
Unable to construct record instance, the following exception occured: null
org.apache.poi.hssf.record.RecordFactory:createRecord:237
org.apache.poi.hssf.record.RecordFactory:createRecords:160
org.apache.poi.hssf.usermodel.HSSFWorkbook:<init>:163
org.apache.poi.hssf.usermodel.HSSFWorkbook:<init>:130
com.lucent.arno.appapi.converter.ExcelToXMLConverter:convert:41
com.lucent.arno.fe.generic.action.messages.bulkload.BulkUpLoadAction:doAction:86
com.lucent.arno.fe.generic.utils.GMSNewActionBase:execute:73
org.apache.struts.action.RequestProcessor:processActionPerform:425
org.apache.struts.action.RequestProcessor:process:228
org.apache.struts.action.ActionServlet:process:1913
org.apache.struts.action.ActionServlet:doPost:462
javax.servlet.http.HttpServlet:service:647
javax.servlet.http.HttpServlet:service:729
sun.reflect.NativeMethodAccessorImpl:invoke0:-2
sun.reflect.NativeMethodAccessorImpl:invoke:39
sun.reflect.DelegatingMethodAccessorImpl:invoke:25
java.lang.reflect.Method:invoke:597
org.apache.catalina.security.SecurityUtil$1:run:244
java.security.AccessController:doPrivileged:-2
javax.security.auth.Subject:doAsPrivileged:517
org.apache.catalina.security.SecurityUtil:execute:276
org.apache.catalina.security.SecurityUtil:doAsPrivilege:162
org.apache.catalina.core.ApplicationFilterChain:internalDoFilter:262
org.apache.catalina.core.ApplicationFilterChain:access$000:52
org.apache.catalina.core.ApplicationFilterChain$1:run:171
java.security.AccessController:doPrivileged:-2
org.apache.catalina.core.ApplicationFilterChain:doFilter:167
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:378
org.springframework.security.intercept.web.FilterSecurityInterceptor:invoke:109
org.springframework.security.intercept.web.FilterSecurityInterceptor:doFilter:83
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.ui.ExceptionTranslationFilter:doFilterHttp:101
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.providers.anonymous.AnonymousProcessingFilter:doFilterHttp:105
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.ui.rememberme.RememberMeProcessingFilter:doFilterHttp:116
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.wrapper.SecurityContextHolderAwareRequestFilter:doFilterHttp:91
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.ui.basicauth.BasicProcessingFilter:doFilterHttp:174
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.ui.AbstractProcessingFilter:doFilterHttp:277
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
com.lucent.arno.fe.generic.filter.SecureLoginFilter:doFilter:127
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.ui.logout.LogoutFilter:doFilterHttp:89
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.context.HttpSessionContextIntegrationFilter:doFilterHttp:235
org.springframework.security.ui.SpringSecurityFilter:doFilter:53
org.springframework.security.util.FilterChainProxy$VirtualFilterChain:doFilter:390
org.springframework.security.util.FilterChainProxy:doFilter:175
org.springframework.web.filter.DelegatingFilterProxy:invokeDelegate:183
org.springframework.web.filter.DelegatingFilterProxy:doFilter:138
sun.reflect.GeneratedMethodAccessor74:invoke:-1
sun.reflect.DelegatingMethodAccessorImpl:invoke:25
java.lang.reflect.Method:invoke:597
org.apache.catalina.security.SecurityUtil$1:run:244
java.security.AccessController:doPrivileged:-2
javax.security.auth.Subject:doAsPrivileged:517
org.apache.catalina.security.SecurityUtil:execute:276
org.apache.catalina.security.SecurityUtil:doAsPrivilege:218
org.apache.catalina.core.ApplicationFilterChain:internalDoFilter:210
org.apache.catalina.core.ApplicationFilterChain:access$000:52
org.apache.catalina.core.ApplicationFilterChain$1:run:171
java.security.AccessController:doPrivileged:-2
org.apache.catalina.core.ApplicationFilterChain:doFilter:167
org.apache.catalina.core.StandardWrapperValve:invoke:213
org.apache.catalina.core.StandardContextValve:invoke:172
org.apache.catalina.core.StandardHostValve:invoke:127
org.apache.catalina.valves.ErrorReportValve:invoke:117
org.apache.catalina.core.StandardEngineValve:invoke:108
org.apache.catalina.connector.CoyoteAdapter:service:174
org.apache.coyote.http11.Http11Processor:process:875
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler:processConnection:665
org.apache.tomcat.util.net.PoolTcpEndpoint:processSocket:528
org.apache.tomcat.util.net.LeaderFollowerWorkerThread:runIt:81
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable:run:689
java.lang.Thread:run:619
Comment 1 dave.sprague 2010-03-18 22:42:22 UTC 
I've discovered an issue (that appears to be similar to this issue) within an application that we have build (using POI 3.6). I can provide examples as needed, but is this specific issue slated for inclusion within POI 3.7?

Thanks,

Dave Sprague
Director, Product Management
Trintech
Comment 2 dave.sprague 2010-03-26 21:12:30 UTC 
Trintech is supplying a zip file with examples. Please review file entitled
220110 Recon 0210Genmed.xls to determine if this issue is related.
Comment 3 dave.sprague 2010-03-26 21:13:13 UTC 
Created attachment 25194 [details]
Trintech_POI examples.zip
Comment 4 Yegor Kozlov 2010-08-10 14:22:11 UTC 
The problem is not reproducible with current trunk. POI can read the attached file (220110 Recon 0210Genmed.xls) and write it back to file without any problem.

Yegor