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:[EMAIL PROTECTED] 
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:[EMAIL PROTECTED]
>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:[EMAIL PROTECTED]
> > 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:[EMAIL PROTECTED]
> > Gesendet: Montag, 15. März 2004 16:42
> > An: [EMAIL PROTECTED]
> > 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: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to