Bug #1416

Updated by Sebastien Jacquot almost 4 years ago

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 ?

h3. Solution 0

Set more Java memory when launching Tomcat :
edit /etc/init.d/tomcat6

# Escape any double quotes in the value of JAVA_OPTS

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")

h3. 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 objects

This 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.

h3. Solution 1

- Be able to diagnose what causes the heap exception
- fix the heap causes