Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0008987Openbravo ERPA. Platformpublic2009-05-11 13:082009-05-19 00:00
jpabloae 
alostale 
urgentmajorsometimes
closedno change required 
30Gentoo - 2.6.18
pi 
 
Core
No
0008987: GC overhead limit exceeded in compileSqlc
Many times we get a "[javac] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded" error in the compileSqlc part.

It is not 100% reproducible, it just happens sometimes. This a 64bit system with the following ANT_OPTS values:
-Xms256m -Xmx1384m -XX:MaxPermSize=256m

We've also tries adding the "-XX:-UseGCOverheadLimit" option, with the same results.


Full log attached.

--
compileSqlc:
    [javac] Compiling 1538 source files to /srv/hudson/jobs/erp_devel_pi-full-pgsql/workspace/build/classes
    [javac] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
    [javac] at java.util.HashMap.addEntry(HashMap.java:753)
    [javac] at java.util.HashMap.put(HashMap.java:385)
    [javac] at java.util.ListResourceBundle.loadLookup(ListResourceBundle.java:180)
    [javac] at java.util.ListResourceBundle.handleGetObject(ListResourceBundle.java:106)
    [javac] at java.util.ResourceBundle.getObject(ResourceBundle.java:378)
    [javac] at java.util.ResourceBundle.getString(ResourceBundle.java:344)
    [javac] at com.sun.tools.javac.util.Messages.getLocalizedString(Messages.java:129)
    [javac] at com.sun.tools.javac.util.Messages.getLocalizedString(Messages.java:80)
    [javac] at com.sun.tools.javac.main.Main.getLocalizedString(Main.java:448)
    [javac] at com.sun.tools.javac.main.Main.resourceMessage(Main.java:421)
    [javac] at com.sun.tools.javac.main.Main.compile(Main.java:364)
    [javac] at com.sun.tools.javac.main.Main.compile(Main.java:279)
    [javac] at com.sun.tools.javac.main.Main.compile(Main.java:270)
    [javac] at com.sun.tools.javac.Main.compile(Main.java:69)
    [javac] at com.sun.tools.javac.Main.main(Main.java:54)
The buildmaxmemory setting of the build.xml file looks suspicious.
250mp2
gz build76.txt.gz (23,142) 2009-05-11 13:08
https://issues.openbravo.com/file_download.php?file_id=1292&type=bug
Issue History
2009-05-11 13:08jpabloaeNew Issue
2009-05-11 13:08jpabloaeAssigned To => rafaroda
2009-05-11 13:08jpabloaeFile Added: build76.txt.gz
2009-05-11 13:08jpabloaeRegression testing => No
2009-05-11 13:09jpabloaeOS VersionGentoo - 2.6.26 => Gentoo - 2.6.18
2009-05-11 13:10shuehnerIssue Monitored: shuehner
2009-05-11 14:07gnuyogaIssue Monitored: gnuyoga
2009-05-11 14:07gnuyogaIssue End Monitor: gnuyoga
2009-05-11 14:08gnuyogaIssue Monitored: gnuyoga
2009-05-11 19:51pjuvaraNote Added: 0016282
2009-05-11 19:51pjuvaraPriorityhigh => urgent
2009-05-14 17:52psarobeStatusnew => scheduled
2009-05-14 17:52psarobeAssigned Torafaroda => alostale
2009-05-14 17:52psarobefix_in_branch => pi
2009-05-14 17:52psarobeTag Attached: 250mp2
2009-05-18 13:12iciordiaAssigned Toalostale => shuehner
2009-05-18 17:25alostaleAssigned Toshuehner => alostale
2009-05-18 17:31alostaleNote Added: 0016434
2009-05-18 17:31alostaleStatusscheduled => closed
2009-05-18 17:31alostaleResolutionopen => no change required
2009-05-19 00:00anonymoussf_bug_id0 => 2793559

Notes
(0016282)
pjuvara   
2009-05-11 19:51   
Upgrading priority as this affects the reliability of the CI framework
(0016434)
alostale   
2009-05-18 17:31   
It seems that increasing the build.maxmemory property in main build.xml from 512M to 1024M solves the problem.

It is being tested in CI and since it was changed it didn't appear again.

Anyway, as this issue rarely appears it is not going to be changed in core since it would change the minimun requirements as well and can be easily work-arrounded.