We have been trying to use the Mirth Connect docker container for some integration projects for a few months now. We see that the memory use goes up over time and always eventually crashes.
When you stop sending messages to the channel, the memory use doesn't go down. As if garbage collection doesn't run? Then when you start sending messages again, it picks up increasing the memory footprint right from where it left off.
Everyone talks about increasing the JVM heap, which we've done multiple times and set to even absurd values. But if JVM doesn't recover old memory, the heap memory limit is irrelevant, you're just buying time before it crashes.
What JVM properties or Mirth configurations have you done to recover unused memory to keep the container stable?
eventually crashes
means that it dies withcgroup limit
? If so, start by reading this for example. – Eugene