Open cayter opened 2 years ago
OS: Ubuntu 20.04.3
Hello, I have the same problem, elasticMQ version 1.3.6 is located in a docker container. It uses 2.4GB of memory after that it stops working but the container does not terminate.
Log:
[elasticmq-akka.actor.default-dispatcher-4] INFO akka.actor.DeadLetterActorRef - Message [org.elasticmq.MessageData] to Actor[akka://elasticmq/deadLetters] was not delivered. [32] dead letters encountered, of which 21 were not logged. The counter will be reset now. If this is not an expected behavior then Actor[akka://elasticmq/deadLetters] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "elasticmq-scheduler-1"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "elasticmq-akka.io.pinned-dispatcher-7"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "elasticmq-akka.actor.default-dispatcher-12"
OS: MacOS Big Sur 11.6.1
Running the docker image locally and use
docker stats
to inspect the memory usage, it just keeps increasing until it runs out of assigned memory and crashes that leads to restart. Is there any configuration we need to add to avoid this?