Mirth Connect 4.3.0 Released!

Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Java virtual machine running out of memory...

  • Filter
  • Time
  • Show
Clear All
new posts

  • Java virtual machine running out of memory...

    Hi guys,

    I'm currently developing some Mirth destinations to be deployed in a hospital environment and have encountered an error when deploying my channels for testing:

    WARN  2007-02-09 15:21:27,890 [SslListener0-1] org.mortbay.jetty.servlet.ServletHandler: Error for /channels
    java.lang.OutOfMemoryError: Java heap space
    Here are the specs of my development machine:

    Windows XP SP2
    Microsoft SQL Server 2005 Express
    Java RE 1.5
    Mirth 1.3.2

    AMD Opteron Dual Core 1.8ghz CPU
    512MB RAM

    It is my suspicion that the memory consumed during the deployment of channels is not sufficiently free'd back to the memory pool once a channel stops deployment. I came to this conclusion when I noticed this error only occurred after frequent deployments of the same channel I was developing and testing and it is also well known that the automatic garbage collection is not the best in the java virtual machine.

    Has anyone else had this problem? if so, how did you get around it? Also, does this problem occur during on-site usage of mirth? in which the mirth server has to remain online for long periods of time without rebooting and a chance for a full flush of the jvm memory space.

    Would it be possible to invoke the System.gc / manual garbage collection command within javascript inside mirth to counteract this problem?

  • #2
    Re: Java virtual machine running out of memory...

    Mirth by default limits the maximum heap space it will use to 64 MB. If you need more than that you should consider going into the conf/wrapper.conf file located in the Mirth directory to change it to a higher value.


    • #3
      Re: Java virtual machine running out of memory...

      You can also adjust the Java memory settings in Mirth.bat (or I believe the argument is -Xmm512 (or any other value)

      Chris Lang