• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Java OOM error

    Hardware
    2
    3
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jeremyhJ
      jeremyh
      last edited by

      Hi there,

      I have a test install of Mango 3.1.1 running in an AWS t2.micro (free tier) instance, with 512MB memory. Approx every week or so Mango will crash because Java runs out of memory:

      Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f65c452d000, 12288, 0) failed; error='Cannot allocate memory' (errno=12)
      #
      # There is insufficient memory for the Java Runtime Environment to continue.
      # Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.
      # An error report file with more information is saved as:
      # /opt/mango/hs_err_pid25504.log
      

      I am running Ubuntu 14.04.05 LTS with:

      # JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode linux-amd64 compressed oops)
      

      Is there any suggested way I can configure Java (or Mango) so that it runs more happily on this server?

      I should also add that I am running another application on this server (a PHP-based network monitor called LibreNMS) which I'm sure is not helping things.

      Thanks!

      1 Reply Last reply Reply Quote 0
      • JoelHaggarJ
        JoelHaggar
        last edited by

        Two things that might help.

        1. Go to the Internal Metrics page and check to see how much memory Mango has to work with.

        2. you can use a start up extension: https://help.infiniteautomation.com/using-startup-extensions/ to assign more memory to Mango. You have to be careful as the OS needs memory too and with only 512 mb ram you don't have much to play with. I would normally use a minimum of 1gb of ram and we have many Amazon installs like this running fine.

        1 Reply Last reply Reply Quote 0
        • jeremyhJ
          jeremyh
          last edited by

          Great, thanks Joel – I'll check that out. Mango reports that the JVM free memory is 144 MB and JVM maximum available memory is 241 MB.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post