Issue
An AS-P (SpaceLogic Server) is crashing; just before the crash, the memory usage in the AS-P increases until it reaches a level where the AS-P crash.
Product Line
EcoStruxure Building Operation
Environment
Building Operation Automation Server Premium (AS-P)
Cause
The issue was caused by a Notification report which was located in the ES to which the AS-P was connected, Every time this report was run, the AS-P crashed after a while.
This report included a search of all Modbus points in the system and all properties of the Modbus points.
When running the report, the ES was setting up a lot of subscriptions to the AS-P in a very short time period. The AS-P could not handle this huge amount of subscriptions and crashed after a while when trying to process all subscriptions from the ES.
Resolution
In this particular case, the AS-P had around 2000 Modbus points.
When the Notification report was running, the search for these 2000 Modbus points and all properties, which were around 20 per Modbus point, caused the ES to set up around 40 000 (2000*20) subscriptions to the AS-P in a very short time period, and it crashed.
To solve this issue, the number of Modbus points in the AS-P was reduced to below 1000, and then the AS-P could handle the number of subscriptions (1000*20=20000) with no crash.
When running a Notification report, including a search, be careful not to search for too many objects and properties in the same report, like in the example above when a search was done for all Modbus objects and properties in an Automation Server.
This is only a problem when a search is done via a Notification report if doing a search from Workstation that is made differently and will not set up a subscription in the same way.
