Bug #1830
GWT: 0.6.1, TIGERSearch query results overload
| Status: | New | Start date: | 07/22/2016 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| 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
- from TXMWEB home logs directry
- the corpus in binary format (the content of the subdirectory of 'corpora') checked with TIGERSearch extension 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
History
#1 Updated by Serge Heiden almost 7 years ago
- Description updated (diff)
#2 Updated by Matthieu Decorde almost 7 years ago
- Description updated (diff)
#3 Updated by Matthieu Decorde almost 7 years ago
- Description updated (diff)
#4 Updated by Serge Heiden almost 7 years ago
- Description updated (diff)
#5 Updated by Alexey Lavrentev over 6 years ago
- Priority changed from Normal to High
#6 Updated by Matthieu Decorde over 6 years ago
- Target version changed from Portal 0.7 to Portal 0.6.2
#7 Updated by Matthieu Decorde over 6 years ago
- % Done changed from 0 to 80
#8 Updated by Matthieu Decorde almost 3 years ago
- % Done changed from 80 to 100