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.

You can reduce the amount of logging by editing the WEB-INF/classes/log4J.xml file. At the bottom of the file you should find this: <root> <level value="info"/> <appender-ref ref="async"/> <appender-ref ref="stdout"/> </root> Change "info" to "warn" or "error", depending on what you want in your logs. You can also edit the category tags. See the log4j documentation for more information about the file. Not sure what the issue with the OPC data source is (i didn't write it). But, out of memory exceptions usually mean that you should allocate more memory to your instance.

not yet, I was on my laptop with verizon wireless connection at a meeting the other night. A couple of them took about 5 to 10 seconds to update when switching between them. although we are also running a virtual box with the old wonderware polling the same points on the same computer... I'll know better next week. I'm on vacation right now...