Java heap space error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. including a data element name from SF with 38 characters in the name
2.
3.

What is the expected output? What do you see instead?
expected "Query is valid" in the result window...instead, get "Exception 
occurred during event dispatching: java.lang.OutOfMemoryError: Java heap space" 
in the dataloader cliq batch session window

What version of the product are you using? On what operating system?
1.4.20

Please provide any additional information below.
eliminating long data name corrected the query

Original issue reported on code.google.com by tim.m.h...@bankofamerica.com on 7 Jul 2011 at 5:12

[GoogleCodeExporter]

...continuing testing...problem may not be related to the data element length, 
but something about the specific field creates an error condition...the field 
is a checkbox, but I haven't had problems with other checkboxes, so it's still 
an unknown error...

Original comment by tim.m.h...@bankofamerica.com on 7 Jul 2011 at 7:40

[GoogleCodeExporter]

subsequent testing resulted in the issue not being related to a field or field 
length...for 2 different objects, I needed to split the export into 2 pieces, 
with half the fields on one, and the other half on the other...it seems to be a 
function of the size of the file to be exported, but I haven't determined the 
exact problem, just a work-around...

Original comment by tim.m.h...@bankofamerica.com on 8 Jul 2011 at 12:06

[GoogleCodeExporter]

Hello,
What was the SOQL query you used?

Vijay

Original comment by vijay.swamidass@gmail.com on 28 Jul 2011 at 5:00

[GoogleCodeExporter]

Select Id, 
IsDeleted, 
XXXXX, 
Date_coe__c FROM Opportunity

Where the XXXXX, I had an additional 93 elements from the Opportunity
object listed...
The error I received in the run window was:

Loading GUI...
Exception occurred during event dispatching:
Java.lang.OutOfMemoryError: Java heap space

I assume it may have something to do with our installation parameters,
but I haven't been able to determine what that might be...I've been able
to circumvent the issue by breaking the export into 2 pieces, with half
the variables on one extract, and the other half on the second
extract--not an ideal solution, but workable...

Thanks Vijay.

Tim

Original comment by tim.m.h...@bankofamerica.com on 28 Jul 2011 at 5:27

[GoogleCodeExporter]

It could be a bug in CLIq when handling large queries.

#1) Try this:
1. Create the export and enter your query:
Select Id, 
IsDeleted, 
XXXXX, 
Date_coe__c FROM Opportunity
LIMIT 10

(You can try to add in all the fields)

2. Generate the CLIq files
3. Edit the process-conf.xml and remove the "LIMIT 10"
4. Run the process

It is possible that the query result is too big for CLIq.

#2) As a workaround, you could also edit cliq.sh (or cliq.bat) and increase the 
max memory settings by adding -Xmx2000m to the java command line.

I'll see if I can reproduce this also.

Original comment by vijay.swamidass@gmail.com on 28 Jul 2011 at 6:03

[GoogleCodeExporter]

Yes, that fixes the scenario...thanks for your help...that's a big
improvement over splitting the object and having to merge it back
together!  Thanks.

Tim

Original comment by tim.m.h...@bankofamerica.com on 28 Jul 2011 at 6:24

[GoogleCodeExporter]

I have set the java heap size to 256m in cliq.sh and cliq.bat.  It will be 
there in the next version.

Original comment by vijay.swamidass@gmail.com on 14 Sep 2011 at 12:36

• Changed state: Fixed