Closed caarto closed 8 years ago
At first sight it seems to me the server was trying to return a too big response and the JVM had not enough heap space to perform the related data compression. To better identify the problem you have to understand what was the causing request and verify how big was the data.
Then try to check your memory settings by running:
$ java -XX:+PrintFlagsFinal -version | grep MaxHeapSize
In case you can try to increase the max heap with the -Xmx
parameter (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html)
Hi @caarto, any news on this?
no enough information to analyze.
closing for now; @caarto reopen it if you find a way to reproduce it.
got same problem, I have 200 documents in a database, each document size is about 160kb and I got a Java Heap OutOfMemory error every time I try to query this collection.
Hi @RusEu , this is a very old issue.
Can you please open a new one with steps to reproduce?
(please note we have several installations with collections with hundreds of thousands of documents, and never had OutOfMemory, it must be something with your server; java isn't able to allocate enough memory.)
hi there: for a long time working, we got a issue in RH in this morning, here is the log
At the same time, we got a tomcat server crash, its log show that the RH did not response in that time,not read time out。