Bug #1830

GWT: 0.6.1, TIGERSearch query results overload

Added by Serge Heiden almost 3 years ago. Updated over 2 years ago.

Status:New Start date:07/22/2016
Priority:High Due date:
Assignee:- % Done:

80%

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

Description

After several TIGERSearch queries, it is impossible to browse results and some TXM commands are unavailable.

Hypothesis

TXM portal memory may be saturated after several TIGERSearch queries.

To diagnose we need:
  • TXM log files described in the "1.14.Consulter les logs du portail" section of the portal admin's manual (p. 13)
    • from TXMWEB home logs directry
      • TXMWEBxxx checked
      • TXMxxx files checked
    • from /var/log/tomcat6
      • catalina_xxx.out files
      • localhost_xxx.txt files
  • the corpus in binary format (the content of the subdirectory of 'corpora') checked with TIGERSearch extension in TXM desktop
Diagnostics should be compared between TIGERSearch access in TXM portal and in TXM desktop:
  • search for the same queries in the two implementations
  • compare the results -> the desktop version may behave differently and have less trouble with memory consumption

Related issues

related to Bug #1416: GWT: 0.6: Java heap space exception New 07/09/2015

History

#1 Updated by Serge Heiden almost 3 years ago

  • Description updated (diff)

#2 Updated by Matthieu Decorde almost 3 years ago

  • Description updated (diff)

#3 Updated by Matthieu Decorde almost 3 years ago

  • Description updated (diff)

#4 Updated by Serge Heiden almost 3 years ago

  • Description updated (diff)

#5 Updated by Alexey Lavrentev over 2 years ago

  • Priority changed from Normal to High

#6 Updated by Matthieu Decorde over 2 years ago

  • Target version changed from Portal 0.7 to Portal 0.6.2

#7 Updated by Matthieu Decorde over 2 years ago

  • % Done changed from 0 to 80

Also available in: Atom PDF