Biztalk - Where did they come from?
Today I had a bizarre experience with a loop in a BizTalk Orchestration that while expected had a unexpected side effect.
In the process of testing an “Error Handling” strategy for a client, I induced an error to happen, accidentally; I forced it into a tail spin by putting it into a tight loop over and over causing the exception until terminating the instance. While I intended to cause an error I didn’t intend to cause the tight loop, that was bonus…
This occurred over about 2 -3 minutes of time.
The bizarre experience begun after this, as BizTalk tried to record the debug trace rows for the orchestration
For almost 30 minutes my SQL server instance ran close to 100% of CPU as it inserted row after row (over 2 million) into the dta_debug_Trace table for the two minute loop
My question that was left un-answered is where does it store these between the time execution generated them and the time they are inserted into the dta_debug_Trace table
None of the BizTalk databases appeared to be the holder of them, and I couldn’t see any significant file I/O. They survived couple of reboots and restarts of the host instance.
So where does it store them ?