thingsboard

Open-source IoT Platform - Device management, data collection, processing and visualization.

dashboard java cloud coap iot iot-analytics iot-platform iot-solutions kafka lwm2m microservices middleware mqtt netty platform snmp thingsboard visualization websockets widgets

History

Sergey Matvienko 062c577d1f Fix infinite loop in rule engine caused by TbRuleChainInputNode self-referencing default rule chain When a TbRuleChainInputNode has `forwardMsgToDefaultRuleChain=true` and the originator's default rule chain is the same as the rule chain containing this node, the message enters an infinite loop: the node forwards to the default rule chain, which routes back to the same node, which forwards again, causing unbounded recursion and 100% CPU on rule-engine. Fix: detect the loop in DefaultTbContext.input() by checking whether the calling rule node is already present in the message's return stack (TbMsgProcessingCtx). On the second+ iteration the stack already contains the (ruleChainId, ruleNodeId) pair of the node, so the call is a cycle. In that case tellFailure() is called with a descriptive message and a WARN log is emitted instead of re-enqueuing the message. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	3 months ago
..
src	Fix infinite loop in rule engine caused by TbRuleChainInputNode self-referencing default rule chain	3 months ago
pom.xml	Version changed to 4.2.2	4 months ago

Sergey Matvienko 062c577d1f Fix infinite loop in rule engine caused by TbRuleChainInputNode self-referencing default rule chain

When a TbRuleChainInputNode has `forwardMsgToDefaultRuleChain=true` and the originator's
default rule chain is the same as the rule chain containing this node, the message enters
an infinite loop: the node forwards to the default rule chain, which routes back to the
same node, which forwards again, causing unbounded recursion and 100% CPU on rule-engine.

Fix: detect the loop in DefaultTbContext.input() by checking whether the calling rule node
is already present in the message's return stack (TbMsgProcessingCtx). On the second+
iteration the stack already contains the (ruleChainId, ruleNodeId) pair of the node,
so the call is a cycle. In that case tellFailure() is called with a descriptive message
and a WARN log is emitted instead of re-enqueuing the message.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

3 months ago

src

Fix infinite loop in rule engine caused by TbRuleChainInputNode self-referencing default rule chain

3 months ago

pom.xml

Version changed to 4.2.2

4 months ago