Skip to main content
1-Visitor
December 17, 2018
Question

ThingWorx Azure IoT Hub Connector Crashing

  • December 17, 2018
  • 9 replies
  • 4465 views

Hi,

 

My TW Connector crashes after a while. This is the error I get:

# 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/Thingworx-Azure-IoT-Hub-Connector-2.0.0.141/connector/bin/hs_err_pid15517.log

# [ timer expired, abort... ]

Aborted (core dumped)

 

At first site this looks like a memory lead for me. The Connector runs on a VM (7GB Memory) and I think the resources should be enough for a dev env. I have connected just one agent and there is not much stress on the Connector. 

 

Are there are any Java settings recommended for running the Azure Connector?

 

Thanks

9 replies

15-Moonstone
December 18, 2018

The error message:

# There is insufficient memory for the Java Runtime Environment to continue.

# Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.

is indicating that JVM is not able to allocate physical memory in your system. 

 

before running ioT Connector find out how much free memory is available in your system using top and sort by resident memory (upper-case letter O, then q), and possibly stop some of them to free up more for running IoT Connector in JVM.

 

stanislav1-VisitorAuthor
1-Visitor
December 20, 2018

I was not able to identify the process using top, but I have the resource usage from thingworx:

Screen Shot 2018-12-20 at 18.37.13.png

15-Moonstone
December 31, 2018

The issue is not with ThingWorx rather your OS not able to allocate memory so output from Thingworx  resource usage page is not helpful. Can you provide output from top as explained earlier instead?

 

Logical and most likely solution to update memory in your VM as 7GB doesn't seams to be enough to run whatever processes you have running.