You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@poi.apache.org by Karl-Heinz Zengerle <ka...@sawag.com> on 2004/03/15 16:42:05 UTC

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

AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Srinadh.

What commands did you use for running it outside Eclipse?

Unfortunately then the debugger which is so good and so much time-safing
will not be useable. Where you narrowing down the problem with
System.out.prinln() a lot?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Srinadh Karumuri [mailto:skarumur@bbn.com] 
Gesendet: Donnerstag, 18. März 2004 15:53
An: POI Users List
Betreff: Re: AW: AW: can't open workbook

BTW,

You can try testing it on the command line and see if Eclipse got
anything 
to do with it.

I had some other issue running through Eclipse and this method helped me

narrow down the problem.

Sri
At 08:49 AM 3/18/2004, Karl-Heinz Zengerle wrote:
>Hi Avik.
>
>The Excel file has 3 MB. The Java VM has 256 MB. In that case
>(JSP-Tomcat) it runs successfully.
>
>Eclipse itselfs seems not to react add the added start parameter
>"-vmargs -Xmx256M" (which should increase the max heap size according
to
>the documentation). Even doubling this value didn't help.
>
>Regards,        Karl-Heinz.
>
>
>-----Ursprüngliche Nachricht-----
>Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
>Gesendet: Donnerstag, 18. März 2004 14:40
>An: POI Users List
>Betreff: Re: AW: can't open workbook
>
>What's your file size? How much JVM memory are you using? if you are
>calling from JSP or Eclipse, remember that tomcat(or any other
>container)/eclipse itself will use up a large part of the available
>memory.
>
>Check it out standalone first, then add the amount of heap required to
>get it to run standalone to the heap setting while running tomcat or
>eclipse.
>
>On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > 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(NativeConstructor
A
> > ccessorImpl.java:39)
> >       at
> >
>sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCon
s
> > tructorAccessorImpl.java:27)
> >       at
>java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> >       at
> >
>org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.jav
a
> > :257)
> >       at
> >
>org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.ja
v
> > 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
> >
>
>
>---------------------------------------------------------------------
>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


---------------------------------------------------------------------
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

Re: AW: AW: can't open workbook

Posted by Srinadh Karumuri <sk...@bbn.com>.
BTW,

You can try testing it on the command line and see if Eclipse got anything 
to do with it.

I had some other issue running through Eclipse and this method helped me 
narrow down the problem.

Sri
At 08:49 AM 3/18/2004, Karl-Heinz Zengerle wrote:
>Hi Avik.
>
>The Excel file has 3 MB. The Java VM has 256 MB. In that case
>(JSP-Tomcat) it runs successfully.
>
>Eclipse itselfs seems not to react add the added start parameter
>"-vmargs -Xmx256M" (which should increase the max heap size according to
>the documentation). Even doubling this value didn't help.
>
>Regards,        Karl-Heinz.
>
>
>-----Ursprüngliche Nachricht-----
>Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
>Gesendet: Donnerstag, 18. März 2004 14:40
>An: POI Users List
>Betreff: Re: AW: can't open workbook
>
>What's your file size? How much JVM memory are you using? if you are
>calling from JSP or Eclipse, remember that tomcat(or any other
>container)/eclipse itself will use up a large part of the available
>memory.
>
>Check it out standalone first, then add the amount of heap required to
>get it to run standalone to the heap setting while running tomcat or
>eclipse.
>
>On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > 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
> >
>
>
>---------------------------------------------------------------------
>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


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

AW: AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Rob.

It's passing the critical point now (run/debug; tab where you can set
the parameter; vm args: -Xmx256m).

Thanks to everybody for the big help,

Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Robert Lowe [mailto:rmlowe@rmlowe.com] 
Gesendet: Donnerstag, 18. März 2004 17:33
An: POI Users List
Betreff: RE: AW: AW: AW: can't open workbook

> Do we mean the same? The settings for the launched application if I
call
> run or debug?
>
> When I understand you right then I just need to set there "-Xmx256m"
and
> possible "-Xss1024k".

Yep, in Eclipse 2.x, go to Run > Run...; click the Arguments tab, and
enter
those settings in the "VM arguments" box.


Best regards,

Robert Lowe
http://RMLowe.com/



---------------------------------------------------------------------
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

AW: AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Rob.

Then I'll test it a.s.a.p. and report the result.

Thanks,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Robert Lowe [mailto:rmlowe@rmlowe.com] 
Gesendet: Donnerstag, 18. März 2004 17:33
An: POI Users List
Betreff: RE: AW: AW: AW: can't open workbook

> Do we mean the same? The settings for the launched application if I
call
> run or debug?
>
> When I understand you right then I just need to set there "-Xmx256m"
and
> possible "-Xss1024k".

Yep, in Eclipse 2.x, go to Run > Run...; click the Arguments tab, and
enter
those settings in the "VM arguments" box.


Best regards,

Robert Lowe
http://RMLowe.com/



---------------------------------------------------------------------
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

RE: AW: AW: AW: can't open workbook

Posted by Robert Lowe <rm...@rmlowe.com>.
> Do we mean the same? The settings for the launched application if I call
> run or debug?
>
> When I understand you right then I just need to set there "-Xmx256m" and
> possible "-Xss1024k".

Yep, in Eclipse 2.x, go to Run > Run...; click the Arguments tab, and enter
those settings in the "VM arguments" box.


Best regards,

Robert Lowe
http://RMLowe.com/



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

AW: AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Rob.

Do we mean the same? The settings for the launched application if I call
run or debug?

When I understand you right then I just need to set there "-Xmx256m" and
possible "-Xss1024k".

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Robert Lowe [mailto:rmlowe@rmlowe.com] 
Gesendet: Donnerstag, 18. März 2004 17:13
An: POI Users List
Betreff: RE: AW: AW: AW: can't open workbook

I think Eclipse always forks a new JVM process when you run a project,
at
least in 2.x.

You can set the default and maximum heap size as JVM options under the
"Run..." options.


Best regards,

Robert Lowe
http://RMLowe.com/



-----Original Message-----
From: Karl-Heinz Zengerle [mailto:karl-heinz.zengerle@sawag.com]
Sent: Thursday, March 18, 2004 11:58 PM
To: 'POI Users List'
Subject: AW: AW: AW: AW: can't open workbook


Hi Avik.

I've counterchecked the documentation and didn't find something which
seems to fit for that forking.

Can you remember that option more detailed?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
Gesendet: Donnerstag, 18. März 2004 16:36
An: POI Users List
Betreff: Re: AW: AW: AW: can't open workbook

No, what I meant is, AFAIK, when you run a java program from inside
eclipse, (either via JUnit, or using a "main()" method), you can
configure whether you want that java program to run in the same JVM that
is running eclipse, or inside a forked (ie, external) JVM. If you use a
forked JVM, you should be able to set its startup parameters.

Regards
-
Avik


On Thu, 2004-03-18 at 20:41, Karl-Heinz Zengerle wrote:
> Hi Avik.
>
> We call Eclipse the following way:
> 	c:
> 	cd \eclipse
> 	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
> org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86
-showsplash
> c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
>
> So I'ld say that calling Eclipse we first call javaw which then calls
> eclipse and tells it its desired memory.
>
> Regards,	Karl-Heinz.
>
>
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
> Gesendet: Donnerstag, 18. März 2004 16:04
> An: POI Users List
> Betreff: Re: AW: AW: can't open workbook
>
> Are you forking a separate JVM from eclipse to run your tests? That
> might have its own settings.
>
> On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> > Hi Avik.
> >
> > The Excel file has 3 MB. The Java VM has 256 MB. In that case
> > (JSP-Tomcat) it runs successfully.
> >
> > Eclipse itselfs seems not to react add the added start parameter
> > "-vmargs -Xmx256M" (which should increase the max heap size
according
> to
> > the documentation). Even doubling this value didn't help.
> >
> > Regards,	Karl-Heinz.
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
> > Gesendet: Donnerstag, 18. März 2004 14:40
> > An: POI Users List
> > Betreff: Re: AW: can't open workbook
> >
> > What's your file size? How much JVM memory are you using? if you are
> > calling from JSP or Eclipse, remember that tomcat(or any other
> > container)/eclipse itself will use up a large part of the available
> > memory.
> >
> > Check it out standalone first, then add the amount of heap required
to
> > get it to run standalone to the heap setting while running tomcat or
> > eclipse.
> >
> > On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > > 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
> > >
> >
> >
> >
---------------------------------------------------------------------
> > 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
> >
>
>
> ---------------------------------------------------------------------
> 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
>


---------------------------------------------------------------------
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




---------------------------------------------------------------------
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

RE: AW: AW: AW: can't open workbook

Posted by Robert Lowe <rm...@rmlowe.com>.
I think Eclipse always forks a new JVM process when you run a project, at
least in 2.x.

You can set the default and maximum heap size as JVM options under the
"Run..." options.


Best regards,

Robert Lowe
http://RMLowe.com/



-----Original Message-----
From: Karl-Heinz Zengerle [mailto:karl-heinz.zengerle@sawag.com]
Sent: Thursday, March 18, 2004 11:58 PM
To: 'POI Users List'
Subject: AW: AW: AW: AW: can't open workbook


Hi Avik.

I've counterchecked the documentation and didn't find something which
seems to fit for that forking.

Can you remember that option more detailed?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
Gesendet: Donnerstag, 18. März 2004 16:36
An: POI Users List
Betreff: Re: AW: AW: AW: can't open workbook

No, what I meant is, AFAIK, when you run a java program from inside
eclipse, (either via JUnit, or using a "main()" method), you can
configure whether you want that java program to run in the same JVM that
is running eclipse, or inside a forked (ie, external) JVM. If you use a
forked JVM, you should be able to set its startup parameters.

Regards
-
Avik


On Thu, 2004-03-18 at 20:41, Karl-Heinz Zengerle wrote:
> Hi Avik.
>
> We call Eclipse the following way:
> 	c:
> 	cd \eclipse
> 	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
> org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86
-showsplash
> c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
>
> So I'ld say that calling Eclipse we first call javaw which then calls
> eclipse and tells it its desired memory.
>
> Regards,	Karl-Heinz.
>
>
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
> Gesendet: Donnerstag, 18. März 2004 16:04
> An: POI Users List
> Betreff: Re: AW: AW: can't open workbook
>
> Are you forking a separate JVM from eclipse to run your tests? That
> might have its own settings.
>
> On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> > Hi Avik.
> >
> > The Excel file has 3 MB. The Java VM has 256 MB. In that case
> > (JSP-Tomcat) it runs successfully.
> >
> > Eclipse itselfs seems not to react add the added start parameter
> > "-vmargs -Xmx256M" (which should increase the max heap size
according
> to
> > the documentation). Even doubling this value didn't help.
> >
> > Regards,	Karl-Heinz.
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Avik Sengupta [mailto:avik.sengupta@itellix.com]
> > Gesendet: Donnerstag, 18. März 2004 14:40
> > An: POI Users List
> > Betreff: Re: AW: can't open workbook
> >
> > What's your file size? How much JVM memory are you using? if you are
> > calling from JSP or Eclipse, remember that tomcat(or any other
> > container)/eclipse itself will use up a large part of the available
> > memory.
> >
> > Check it out standalone first, then add the amount of heap required
to
> > get it to run standalone to the heap setting while running tomcat or
> > eclipse.
> >
> > On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > > 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
> > >
> >
> >
> >
---------------------------------------------------------------------
> > 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
> >
>
>
> ---------------------------------------------------------------------
> 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
>


---------------------------------------------------------------------
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




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

AW: AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Avik.

I've counterchecked the documentation and didn't find something which
seems to fit for that forking.

Can you remember that option more detailed?

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
Gesendet: Donnerstag, 18. März 2004 16:36
An: POI Users List
Betreff: Re: AW: AW: AW: can't open workbook

No, what I meant is, AFAIK, when you run a java program from inside
eclipse, (either via JUnit, or using a "main()" method), you can
configure whether you want that java program to run in the same JVM that
is running eclipse, or inside a forked (ie, external) JVM. If you use a
forked JVM, you should be able to set its startup parameters. 

Regards
-
Avik


On Thu, 2004-03-18 at 20:41, Karl-Heinz Zengerle wrote:
> Hi Avik.
> 
> We call Eclipse the following way:
> 	c:
> 	cd \eclipse
> 	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
> org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86
-showsplash
> c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
> 
> So I'ld say that calling Eclipse we first call javaw which then calls
> eclipse and tells it its desired memory.
> 
> Regards,	Karl-Heinz.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> Gesendet: Donnerstag, 18. März 2004 16:04
> An: POI Users List
> Betreff: Re: AW: AW: can't open workbook
> 
> Are you forking a separate JVM from eclipse to run your tests? That
> might have its own settings. 
> 
> On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> > Hi Avik.
> > 
> > The Excel file has 3 MB. The Java VM has 256 MB. In that case
> > (JSP-Tomcat) it runs successfully.
> > 
> > Eclipse itselfs seems not to react add the added start parameter
> > "-vmargs -Xmx256M" (which should increase the max heap size
according
> to
> > the documentation). Even doubling this value didn't help.
> > 
> > Regards,	Karl-Heinz.
> > 
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> > Gesendet: Donnerstag, 18. März 2004 14:40
> > An: POI Users List
> > Betreff: Re: AW: can't open workbook
> > 
> > What's your file size? How much JVM memory are you using? if you are
> > calling from JSP or Eclipse, remember that tomcat(or any other
> > container)/eclipse itself will use up a large part of the available
> > memory. 
> > 
> > Check it out standalone first, then add the amount of heap required
to
> > get it to run standalone to the heap setting while running tomcat or
> > eclipse. 
> > 
> > On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > > 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
> > > 
> > 
> > 
> >
---------------------------------------------------------------------
> > 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
> > 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


---------------------------------------------------------------------
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

AW: AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Thanks Avik.

I've understood.

For debugging reasons I use a main() whereas from the JSP page it starts
at a deeper level. So I look what can be set there.

Where I can set the parameters there's also a field VM arguments. This
seems to be the fitting one.

As soon as I've tested it I'll report about the result.

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
Gesendet: Donnerstag, 18. März 2004 16:36
An: POI Users List
Betreff: Re: AW: AW: AW: can't open workbook

No, what I meant is, AFAIK, when you run a java program from inside
eclipse, (either via JUnit, or using a "main()" method), you can
configure whether you want that java program to run in the same JVM that
is running eclipse, or inside a forked (ie, external) JVM. If you use a
forked JVM, you should be able to set its startup parameters. 

Regards
-
Avik


On Thu, 2004-03-18 at 20:41, Karl-Heinz Zengerle wrote:
> Hi Avik.
> 
> We call Eclipse the following way:
> 	c:
> 	cd \eclipse
> 	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
> org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86
-showsplash
> c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
> 
> So I'ld say that calling Eclipse we first call javaw which then calls
> eclipse and tells it its desired memory.
> 
> Regards,	Karl-Heinz.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> Gesendet: Donnerstag, 18. März 2004 16:04
> An: POI Users List
> Betreff: Re: AW: AW: can't open workbook
> 
> Are you forking a separate JVM from eclipse to run your tests? That
> might have its own settings. 
> 
> On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> > Hi Avik.
> > 
> > The Excel file has 3 MB. The Java VM has 256 MB. In that case
> > (JSP-Tomcat) it runs successfully.
> > 
> > Eclipse itselfs seems not to react add the added start parameter
> > "-vmargs -Xmx256M" (which should increase the max heap size
according
> to
> > the documentation). Even doubling this value didn't help.
> > 
> > Regards,	Karl-Heinz.
> > 
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> > Gesendet: Donnerstag, 18. März 2004 14:40
> > An: POI Users List
> > Betreff: Re: AW: can't open workbook
> > 
> > What's your file size? How much JVM memory are you using? if you are
> > calling from JSP or Eclipse, remember that tomcat(or any other
> > container)/eclipse itself will use up a large part of the available
> > memory. 
> > 
> > Check it out standalone first, then add the amount of heap required
to
> > get it to run standalone to the heap setting while running tomcat or
> > eclipse. 
> > 
> > On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > > 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
> > > 
> > 
> > 
> >
---------------------------------------------------------------------
> > 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
> > 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


---------------------------------------------------------------------
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

Re: AW: AW: AW: can't open workbook

Posted by Avik Sengupta <av...@itellix.com>.
No, what I meant is, AFAIK, when you run a java program from inside
eclipse, (either via JUnit, or using a "main()" method), you can
configure whether you want that java program to run in the same JVM that
is running eclipse, or inside a forked (ie, external) JVM. If you use a
forked JVM, you should be able to set its startup parameters. 

Regards
-
Avik


On Thu, 2004-03-18 at 20:41, Karl-Heinz Zengerle wrote:
> Hi Avik.
> 
> We call Eclipse the following way:
> 	c:
> 	cd \eclipse
> 	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
> org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash
> c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
> 
> So I'ld say that calling Eclipse we first call javaw which then calls
> eclipse and tells it its desired memory.
> 
> Regards,	Karl-Heinz.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> Gesendet: Donnerstag, 18. März 2004 16:04
> An: POI Users List
> Betreff: Re: AW: AW: can't open workbook
> 
> Are you forking a separate JVM from eclipse to run your tests? That
> might have its own settings. 
> 
> On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> > Hi Avik.
> > 
> > The Excel file has 3 MB. The Java VM has 256 MB. In that case
> > (JSP-Tomcat) it runs successfully.
> > 
> > Eclipse itselfs seems not to react add the added start parameter
> > "-vmargs -Xmx256M" (which should increase the max heap size according
> to
> > the documentation). Even doubling this value didn't help.
> > 
> > Regards,	Karl-Heinz.
> > 
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> > Gesendet: Donnerstag, 18. März 2004 14:40
> > An: POI Users List
> > Betreff: Re: AW: can't open workbook
> > 
> > What's your file size? How much JVM memory are you using? if you are
> > calling from JSP or Eclipse, remember that tomcat(or any other
> > container)/eclipse itself will use up a large part of the available
> > memory. 
> > 
> > Check it out standalone first, then add the amount of heap required to
> > get it to run standalone to the heap setting while running tomcat or
> > eclipse. 
> > 
> > On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > > 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
> > > 
> > 
> > 
> > ---------------------------------------------------------------------
> > 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
> > 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


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

AW: AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Avik.

We call Eclipse the following way:
	c:
	cd \eclipse
	C:\j2sdk1.4.1_05\bin\javaw.exe -cp c:\eclipse\startup.jar
org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash
c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600

So I'ld say that calling Eclipse we first call javaw which then calls
eclipse and tells it its desired memory.

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
Gesendet: Donnerstag, 18. März 2004 16:04
An: POI Users List
Betreff: Re: AW: AW: can't open workbook

Are you forking a separate JVM from eclipse to run your tests? That
might have its own settings. 

On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> Hi Avik.
> 
> The Excel file has 3 MB. The Java VM has 256 MB. In that case
> (JSP-Tomcat) it runs successfully.
> 
> Eclipse itselfs seems not to react add the added start parameter
> "-vmargs -Xmx256M" (which should increase the max heap size according
to
> the documentation). Even doubling this value didn't help.
> 
> Regards,	Karl-Heinz.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> Gesendet: Donnerstag, 18. März 2004 14:40
> An: POI Users List
> Betreff: Re: AW: can't open workbook
> 
> What's your file size? How much JVM memory are you using? if you are
> calling from JSP or Eclipse, remember that tomcat(or any other
> container)/eclipse itself will use up a large part of the available
> memory. 
> 
> Check it out standalone first, then add the amount of heap required to
> get it to run standalone to the heap setting while running tomcat or
> eclipse. 
> 
> On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > 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
> > 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


---------------------------------------------------------------------
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

Re: AW: AW: can't open workbook

Posted by Avik Sengupta <av...@itellix.com>.
Are you forking a separate JVM from eclipse to run your tests? That
might have its own settings. 

On Thu, 2004-03-18 at 19:19, Karl-Heinz Zengerle wrote:
> Hi Avik.
> 
> The Excel file has 3 MB. The Java VM has 256 MB. In that case
> (JSP-Tomcat) it runs successfully.
> 
> Eclipse itselfs seems not to react add the added start parameter
> "-vmargs -Xmx256M" (which should increase the max heap size according to
> the documentation). Even doubling this value didn't help.
> 
> Regards,	Karl-Heinz.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
> Gesendet: Donnerstag, 18. März 2004 14:40
> An: POI Users List
> Betreff: Re: AW: can't open workbook
> 
> What's your file size? How much JVM memory are you using? if you are
> calling from JSP or Eclipse, remember that tomcat(or any other
> container)/eclipse itself will use up a large part of the available
> memory. 
> 
> Check it out standalone first, then add the amount of heap required to
> get it to run standalone to the heap setting while running tomcat or
> eclipse. 
> 
> On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> > 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
> > 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


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

AW: AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
Hi Avik.

The Excel file has 3 MB. The Java VM has 256 MB. In that case
(JSP-Tomcat) it runs successfully.

Eclipse itselfs seems not to react add the added start parameter
"-vmargs -Xmx256M" (which should increase the max heap size according to
the documentation). Even doubling this value didn't help.

Regards,	Karl-Heinz.


-----Ursprüngliche Nachricht-----
Von: Avik Sengupta [mailto:avik.sengupta@itellix.com] 
Gesendet: Donnerstag, 18. März 2004 14:40
An: POI Users List
Betreff: Re: AW: can't open workbook

What's your file size? How much JVM memory are you using? if you are
calling from JSP or Eclipse, remember that tomcat(or any other
container)/eclipse itself will use up a large part of the available
memory. 

Check it out standalone first, then add the amount of heap required to
get it to run standalone to the heap setting while running tomcat or
eclipse. 

On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> 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
> 


---------------------------------------------------------------------
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

Re: AW: can't open workbook

Posted by Avik Sengupta <av...@itellix.com>.
What's your file size? How much JVM memory are you using? if you are
calling from JSP or Eclipse, remember that tomcat(or any other
container)/eclipse itself will use up a large part of the available
memory. 

Check it out standalone first, then add the amount of heap required to
get it to run standalone to the heap setting while running tomcat or
eclipse. 

On Wed, 2004-03-17 at 16:44, Karl-Heinz Zengerle wrote:
> 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
> 


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

AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
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

AW: can't open workbook

Posted by Karl-Heinz Zengerle <ka...@sawag.com>.
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