GWT: 0.6: Java heap space exception
Occurs sometimes :
- at startup
- when using TIGERSearch
- when computing Index or Lexicon of Partition with a lot of parts
- at TBX initialization when relaunching the war after a previously Java Heap Space Exception
- more ?
Solution 0
Set more Java memory when launching Tomcat :
edit /etc/init.d/tomcat6
after:
# Escape any double quotes in the value of JAVA_OPTS
set:
JAVA_OPTS="-Djava.awt.headless=true -Xms512m -Xmx4096m -XX:PermSize=256m -XX:MaxPermSize=1024m"(For information, the file /etc/init.d/tomcat6 is the one used when launching Tomcat from “service tomcat6 start”)
Hypothesis 1
Some Java object are not garbaged when the TXM web app is reloaded.
[insert here the tomcat startup logs warning about the not garbaged objectsThis is a known bug, one simple solution is :
- to not reload tomcat apps, but restart tomcat
- to isolate the webapps
This solution is used by the ENS tomcat VMs.
Solution 1
- catch the exception
- be able to diagnose what causes the heap exception
- fix the heap causes
(from redmine: issue id 1416, created on 2015/07/09 by Matthieu Decorde)
- Relations:
- relates #1830 (closed)