Bug #1416

GWT: 0.6: Java heap space exception

Added by Matthieu Decorde about 4 years ago. Updated almost 3 years ago.

Status:New Start date:07/09/2015
Priority:High Due date:
Assignee:- % Done:

0%

Category:Administration Spent time: -
Target version:Portal 0.6.2

Description

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

Solution 1

- catch the exception
- be able to diagnose what causes the heap exception
- fix the heap causes


Related issues

related to Bug #1830: GWT: 0.6.1, TIGERSearch query results overload New 07/22/2016

History

#1 Updated by Sebastien Jacquot almost 4 years ago

  • Description updated (diff)

#2 Updated by Sebastien Jacquot almost 4 years ago

  • Description updated (diff)

#3 Updated by Sebastien Jacquot almost 4 years ago

  • Description updated (diff)

#4 Updated by Alexey Lavrentev almost 3 years ago

  • Target version changed from Portal X.X to Portal 0.7

#5 Updated by Matthieu Decorde almost 3 years ago

  • Target version changed from Portal 0.7 to Portal 0.6.2

#6 Updated by Matthieu Decorde almost 3 years ago

  • Description updated (diff)

Also available in: Atom PDF