Replies: 2 comments
-
What specific errors do you get? The memory setting in the launcher is how much memory the MC client will use when it launches. Larger MC instances (500+ channels) often need ALL THE RAM to function. Most instances are fine on 256-512 MB. This setting is completely disassociated from the settings used by the server to actually run the Mirth server processes. If you do not get any errors, start the launcher by:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Well, for some reason it is no longer giving that error. Working fine with 512 selected. I'll keep these instructions in case it comes back. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For some reason, when I try to start one of our mirth instances (we have 8), I get a heap memory error. Checking the appliance it shows it is only using 45% of available memory. My pc also has plenty of memory available. If I change the heap size to 256 it will start.
Guess I'm not really clear on what this setting it doing or if it is related to the Mirth memory allocation on the appliance or running on my PC. This is the first time I've seen this error when launching MC.
Beta Was this translation helpful? Give feedback.
All reactions