Convert to excel 2.0 hangs on conversion (125k rows)

Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.
4 posts Page 1 of 1


Posts: 12
Joined: Sun Mar 31, 2013 12:13 pm

Post by bothunbr » Mon Apr 15, 2013 4:48 pm

The convert to excel function hangs when I try to convert anything with over 125k rows. Each row has 30 columns. During the conversion we get ultra high CPU and memory usage on the server. I have cranked up max heap to 10g on the 64bit JVM and this process seems to want to use every bit of it.

4/15/13 9:43:09 AM INFO Executing task 'writeExcel 2.0'
4/15/13 9:48:17 AM INFO Finished task 'writeExcel 2.0'
4/15/13 9:48:17 AM ERROR GC overhead limit exceeded
4/15/13 9:48:17 AM INFO Finished project 'Objective2'
4/15/13 9:48:17 AM ERROR GC overhead limit exceeded
com.linoma.dpa.runtime.JobFailedException: GC overhead limit exceeded
at Source)
at com.linoma.dpa.runtime.Runtime.executeProject(Unknown Source)
at com.linoma.dpa.j2ee.forms.ConfigureProjectComponentForm.executeProject(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(

I know, who wants a 125k row excel file anyway. I was just testing the limits of the system and excel should be able to do 1 million rows. The conversion process seems a bit slow even on a smaller file. Maybe I need to tweak something in my JVM?


Posts: 41
Joined: Wed Mar 30, 2011 10:19 am

Post by monahanks » Thu May 16, 2013 8:46 am
We have a similar issue writing to Excel 2007 - error about heap storage or some such thing, and running a long time. Switching back to excel 2003 runs fine and quick. Wish I could answer your post.


Support Specialist
Posts: 592
Joined: Tue Jul 17, 2012 2:12 pm
Location: Phoenix, AZ

Post by Support_Rick » Fri May 24, 2013 1:14 pm

The writeExecl task is a very memory intensive task. It does (and will) take some tweaking on your Java Memory to get something that large to work since it has to load the file into memory to get it to process.

Creating a CSV would be a cleaner (and quicker) alternative and still give you the Spreadsheet entries that you could save into 2003/2007 or later formats.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696


Posts: 1
Joined: Thu May 08, 2014 10:55 pm

Post by Baldwinlee » Fri May 09, 2014 1:29 am
Yes, the issuse that heap storage or some such thing, and running a long time will occur sometimes, and I have met such problem several times. I am not clear that if we change Excel 2007 or exce 2010 to excel 2003, the excel converter will works much better. Can anyone give more useful advice if I still use excel 2007 or any later version.
4 posts Page 1 of 1