[BUG] When trying to access the Mirth channel I am facing a Java Heap space issue #6344
Replies: 2 comments 4 replies
-
This should be a Discussion not an Issue. 2-4GB on the client should be more than enough. When you get the client error you posted, do you also see a server side error in |
Beta Was this translation helpful? Give feedback.
1 reply
-
There are no server side errors seen in mirth.log. Also please note in the organisation at the moment I am the only user who is experiencing this issue. The other users can access the channels successfully. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
While I can access the Mirth dashboard successfully I am unable to access the Mirth channel
Issue seen as below:
java.lang.OutOfMemoryError: Java heap space
com.mirth.connect.client.core.ClientException: java.lang.OutOfMemoryError: Java heap space
at com.mirth.connect.client.core.Client$2.invoke(Client.java:294)
at com.sun.proxy.$Proxy66.getChannelSummary(Unknown Source)
at com.mirth.connect.client.core.Client.getChannelSummary(Client.java:1063)
at com.mirth.connect.client.ui.ChannelPanel.retrieveChannels(ChannelPanel.java:614)
at com.mirth.connect.client.ui.ChannelPanel.retrieveChannels(ChannelPanel.java:608)
at com.mirth.connect.client.ui.ChannelPanel$1.doInBackground(ChannelPanel.java:429)
at com.mirth.connect.client.ui.ChannelPanel$1.doInBackground(ChannelPanel.java:426)
at com.mirth.connect.client.ui.QueuingSwingWorker.doInBackground(QueuingSwingWorker.java:97)
We have tried re-starting the servers as well as increased the heap space to 4GB at the time of launch too but this did not help
Beta Was this translation helpful? Give feedback.
All reactions