Search

"Dead instance" in <MsgBox>.dbo.Instances? by adammeyer

Closed
as By Design Help for as By Design

1
0
Sign in
 to vote
Type: Bug
ID: 576632
Opened: 7/20/2010 2:44:20 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
We detected a different behavior between BizTalk 2010 Beta to BizTalk2006 and we are not sure if it is a bug or if it works as designed.
 
We have a test case in which we force an orchestration instance to be suspended (resumable). Then we fix our environment and resume the suspended orchestration instance. The orchestration will succeed. So far so good.

In BizTalk 2006 when we look after this test case into the internal database <MsgBox>.dbo.Instances we saw that it was empty. But in BizTalk 2010 Beta we see that it contains an item. In the BizTalk Admin Console we do not see an item, it is empty as expected.
 
Our question now is whether this is a bug or is it an expected behavior. If the latter is the case how will that “dead” instance be cleaned up internally or will it stay there forever?
Details (expand)

Product Language

English

Version

BizTalk 2010 Beta

Category

Maintenance/Operations

Repro Steps

see description.
File Attachments
File Name Submitted By Submitted On File Size  
BizTalkMsgDb.zip (restricted) adammeyer 7/20/2010 -
Sign in to post a comment.
Posted by Microsoft on 7/22/2010 at 11:36 PM
Yes, you are right that these are internal instances. They are the instances for the caching service.

These instance can be ignored. The reason you do not see them in MMC is becuase BizTalk code internally filters these, since these are internal details of the caching service.

Thanks for the detailed feedback that you have given.
Posted by adammeyer on 7/22/2010 at 4:06 AM
Hi Rahul,

thank you for the explanation, it helps! But I have one more question to this.

I understand that it is an internal thing, but even if we use a WMI-select query for “Select * FROM MSBTS_MessageInstance” we get these instances. I would expect that WMI works like the HAT tool. Is this also "By Design"?

Thanks for further explanations.
André
Posted by Microsoft on 7/21/2010 at 4:36 AM
These instances are internal instances used by BizTalk and don't correspond/relate to any messages/orchestration instances in the system. There is one such instance corresponding to each host instance in the system, and these instances will remain there as long as the host instance is running.

You can verify this by using the HAT tool in the admin console to see if any message/orchestration instances are visible. You will not see any such instances.

If you stop a host instance, you will see the count of such instances in the table reduce by one. On restarting it, the instance will be recreated with a different ID.

Hope this helps to clarify why we have resolved this as "By Design"

Posted by adammeyer on 7/20/2010 at 11:53 PM
Hi Rahul,

you changed the status to "by design". Please can you give us a short explanation to this?

Thank you in advance,
André
Posted by adammeyer on 7/20/2010 at 5:44 AM
Hi Rahul,

i have attached the backup of a MsgBox in the described state. Thank you for the support!

Regards,
André
Posted by Microsoft on 7/20/2010 at 4:38 AM
Hi,

Thanx for you feedback. Would it be possible for you to provide the instance table content for our investigation?

Regards,
Rahul
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement