poi-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Zengerle" <karl-heinz.zenge...@sawag.com>
Subject AW: can't open workbook
Date Wed, 17 Mar 2004 11:14:56 GMT
Hi world.

We could improve the situation to the following one:

	The things are running being called from a JSP page.
	Being run or debugged in Ecplipse it still crashes with the out
of
	memory error whatever VM memory we use.

All that happens at
      this.oiWB = new HSSFWorkbook(fs);
i.e. when opening the Excel file and not having processed anything in
our application.

Does anybody have a further idea?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Karl-Heinz Zengerle [mailto:karl-heinz.zengerle@sawag.com] 
Gesendet: Montag, 15. März 2004 16:52
An: 'POI Users List'
Betreff: AW: can't open workbook

Hi world.

Without shelter measures we receive an out of memory error now.

So I've the following questions:
	Which Excel things doesn't POI allow?
	Up to about what size normally Excel files can be opened without
	increasing the Java VM memory and without having problems?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Karl-Heinz Zengerle [mailto:karl-heinz.zengerle@sawag.com] 
Gesendet: Montag, 15. März 2004 16:42
An: poi-user@jakarta.apache.org
Betreff: can't open workbook

Hi world,
 
When our application processed the following command
 
      this.oiWB = new HSSFWorkbook(fs);
 
the exception below is thrown.
 
java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
      at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
      at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
      at
org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.java
:257)
      at
org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.jav
a:193)
      at
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:207)
      at
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:174)
<-- POI
      at webCRT.XlCRTImport.<init>(XlCRTImport.java:120)
<-- our application
      at webCRT.XlCRTImport.importCRTFile(XlCRTImport.java:324)
      at webCRT.XlCRTTstImp.TestImportFiles(XlCRTTstImp.java:275)
      at webCRT.XlCRTImport.main(XlCRTImport.java:186)
Caused by: java.lang.IllegalArgumentException: Illegal length
      at
org.apache.poi.util.StringUtil.getFromUnicodeHigh(StringUtil.java:114)
      at
org.apache.poi.hssf.record.FontRecord.fillFields(FontRecord.java:172)
      at org.apache.poi.hssf.record.Record.fillFields(Record.java:127)
      at org.apache.poi.hssf.record.Record.<init>(Record.java:92)
      at
org.apache.poi.hssf.record.FontRecord.<init>(FontRecord.java:125)
      ... 12 more
 
Does anybody have an idea of possible reasons? Opening the workbook is
the first POI action. So it can't be in our application.
 
Since several months small files where all sheets are visible and not
locked in any way the application runs without problems. Now the Excel
file has grown very much (around our basic handling) and some sheets are
hidden and some sheets are locked.
 
Regards,
Karl-Heinz Zengerle
 


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: poi-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: poi-user-help@jakarta.apache.org


Mime
View raw message