EventManager Crash
Posted: 28 Feb 2018, 10:08
Hi,
I'm not sure if this has already been reported or if you are aware, in case you're not, here goes.
There is an issue with the default Event Manager in the SDK. When a monitored item with Where-Clause "Severity=5 && Severity=6" is placed in a subscription, the EventManager leaves two of FilterOperands uninitialized (NULL). Then when an event is fired the SDK tries to evaluate it against NULL operands, and thus crashes the server.
The problem can be replicated with the cpp demo-server and CTT from Foundation's website. Run test 'Base Eventing/Monitor Events/007.js'. It causes the server to crash. The testcase itself is not implemented fully, but it reveals the problem. Alternatively "IsAuditActivated" can be set to "true" in ServerConfig.xml to force event from within sdk (SessionOpenEvent).
SDK Version = vs2012sp4-v1.5.6-361
CTT Version = v1.3.340.380
I'm not sure if this has already been reported or if you are aware, in case you're not, here goes.
There is an issue with the default Event Manager in the SDK. When a monitored item with Where-Clause "Severity=5 && Severity=6" is placed in a subscription, the EventManager leaves two of FilterOperands uninitialized (NULL). Then when an event is fired the SDK tries to evaluate it against NULL operands, and thus crashes the server.
The problem can be replicated with the cpp demo-server and CTT from Foundation's website. Run test 'Base Eventing/Monitor Events/007.js'. It causes the server to crash. The testcase itself is not implemented fully, but it reveals the problem. Alternatively "IsAuditActivated" can be set to "true" in ServerConfig.xml to force event from within sdk (SessionOpenEvent).
SDK Version = vs2012sp4-v1.5.6-361
CTT Version = v1.3.340.380