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.

@phildunlap I used both CSV and Excel, I actually discovered the issue on the csv version, but it works the same for me either way. Emailing files now.

TL;DR If you make an excel template, limit your named ranges to as small as possible Alrighty, so after a few more days of troubleshooting, @phildunlap took a look at my excel template. He determined that the named range I designated in Excel was too long (only by a million cells!) for EACH named range, of which there are about 50. So, the theory was that the POI Apache plugin that allows Mango to interact with Excel was loading these empty cells into memory somehow, and was sporadically causing a memory leak or memory usage at least until the point where it would cripple the amount of available memory to the JVM to VERY VERY low, and render the garbage collection useless. Thats a mouthful. And so, the problem only reared its ugly head once in awhile, it was hard to track down, but I've been operating for about a week now with no "crippling" memory issue, and I've launched thousands of reports without issue. For anyone who wants to know, the final template filled in is 82kb, has charts and 5 sheets of data, the time range spans 14 months and there are multiple different time ranges used and approximately 10-15 data points queried.

I mispoke in my last post, you should be able to use 1 web socket for all your data point values. If you review the web/js/mango-2.0/RealtimeDataProvider.js file in the Dashboards module you can see how this would work. Basically you just need 1 web socket and can then send additional registration requests for each data point you want. The next version of the Dashboards module (1.1.1) will contain an example of how to use 1 web socket for all point values captured within Mango.

There are a few things you need to know about using our REST api from a host other than Mango. You will need to setup the CORS filter to allow cross site requests into Mango. You will need to allow all the various headers that you want to use. Checkout the classes/mangoApiHeaders.properties and the web/dox folder to see how the override-web.xml file should work. Be careful as the early releases of 2.6.0 beta have this filed named web-override.xml (which is wrong). You will need to use the REST api to login to Mango via your remote server and then retain the session cookie to pass back to mango on any future requests. Be sure to include the password header in the CORS configuration as you will most likely need to use this to login. In the future we are planning to use OAUTH but this has not been a high priority for us yet.