RuleSetTranslationComplexityException - Scenario...

October 16, 2004 · 1 min read

I have a large number of messages that are passed into an orchestration/ split in the incoming pipeline and then passed one by one into a Rules Engine policy. I have discovered when I am processing hundreds of instances at once I ocassionally get the following exception raised in HAT.

"Microsoft.RuleEngine.RuleSetTranslationComplexityException

Ruleset is too complex and translation cannot complete within the configured translation timeout interval."

This is because BizTalk 2004 does not throttle the calls to the rules engine and the rules engine queues the inbound message and processes them in FIFO order.

The solution:

"Increase the time out in the registry for the rules engine from 1 minute -> something like 5 minutes"

regedit

My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Business Rules/3.0/

  • default value "60000" (1 minute)

restart Rules Engine Service

VOLA

This article is part of the GWB Archives. Original Author: Nigel Parker

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.