Description
we've observed when indexing a large repository, that over time a large number of index requests fill up the queue, consuming both memory and disk processing. If there is not enough memory allocated, the server can eventually restart, and the indexing will not complete, meaning the queue will fill up again on restart.
This is not a memory leak - if the queue completes all operates as normal. The problem is the queue not being processed quickly enough.
Attachments
Issue Links
- supercedes
-
MRM-1058 Error 500 Unable to load class for JSP
-
- Closed
-