Hi Folks,
I am getting following exceptions while opening worksheet.
POIFSFileSystem fs = new POIFSFileSystem(new FileInputStream(file_path))
HSSFWorkbook wb = new HSSFWorkbook(fs);
HSSFSheet sheet = wb.getSheet("Lists");
[10/14/04 16:10:00:299 IST] 6c226ca4 SystemErr R [WARNING] Unknown Ptg 3c (60)
[10/14/04 16:10:00:800 IST] 6c226ca4 SystemErr R
java.lang.reflect.InvocationTargetException
[10/14/04 16:10:00:800 IST] 6c226ca4 SystemErr R at
sun.reflect.GeneratedConstructorAccessor106.newInstance(Unknown Source)
[10/14/04 16:10:00:800 IST] 6c226ca4 SystemErr R at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled
Code))
[10/14/04 16:10:00:800 IST] 6c226ca4 SystemErr R at
java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
[10/14/04 16:10:00:800 IST] 6c226ca4 SystemErr R at
org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.java(Compiled
Code))
Any one faced this issue please help me..
Thanks in advance. Here is old mail thread..
I went through mail archive. I found some mails suggesting putting some startup
parameters in eclipse path like..
c:\eclipse\eclipse.exe -vmargs -Xmx256M -Xss1024k -showsplash 600
I am using WSAD 5.1.1
How do I configure these parameters in WSAD.... any one faced this issue please help
me..
Thanks in advance. Here is old mail thread..
Regards,
Mahesh.
--------------------------------
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:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
> 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:[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(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: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> >
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
