Microsoft.XLANGs.RuntimeTypes.InvalidPropertyTypeException

We receive Microsoft.XLANGs.RuntimeTypes.InvalidPropertyTypeException during
what appear to be tracking related activities (see call stack below).

However, they still occur when we turn tracking off.

Is this 'exception' of a significant concern? The process doesn't crash,
the messages still get delivered, and the tracking data gets tracked (when
on). However, I'm wondering if there are resources not being cleaned up
properly which would tie it to our out of memory issue?

Any suggestions, comments, or info appreciated!

Sumary info below...

Thanks!
Zach


Background:
This was identified while attempting to discover why we have a BizTalk 2004
host instance, that contains only orchestration related resources, is
experiencing an Out of Memory error in our production environment. There has
been additional load placed on the components involved over the last few
months and it has become an almost daily occurence.

Using Identify AppSight to record against the process I saw an alarming
number of exceptions occuring, however, I wasn't always getting the exception
type information. I still have an outstanding number of exceptions,
primarily unknown or System.FormatExceptions that I'm running down.

However, dropping out to using windows debugging tools/adplus running in
crash mode, dumping on first chance exceptions turned up an awful number of
instances where the exception turns out to be this
InvalidPropertyTypeException.

The !clrstack always looks like this:

0:011> !clrstack
Thread 11
ESP EIP
0b79f608 77e55dea [FRAME: HelperMethodFrame]
0b79f634 1613c135 [DEFAULT] [hasThis] Class
Microsoft.XLANGs.RuntimeTypes.MessagePropertyDefinition
Microsoft.XLANGs.Core.XMessage._getMessagePropertyDefinition(Class
System.Type)
0b79fe40 79babd2b [FRAME: ContextTransitionFrame]

and the !dumpstack is pretty consistent to this:

0:011> !dumpstack
Current frame: kernel32!RaiseException+0x3c
ChildEBP RetAddr Caller,Callee
0b79f520 77e55dea kernel32!RaiseException+0x3c, calling *** ERROR: Symbol
file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!RtlRaiseException
0b79f528 791c6e1f *** ERROR: Symbol file could not be found. Defaulted to
export symbols for mscorsvr.dll -
mscorsvr!Ordinal76+0x16e1f, calling mscorsvr!Ordinal76+0x16da0
0b79f53c 791c6e90 mscorsvr!Ordinal76+0x16e90, calling
mscorsvr!Ordinal76+0x16de2
0b79f554 791c6ea5 mscorsvr!Ordinal76+0x16ea5, calling
mscorsvr!Ordinal76+0x16e7e
0b79f568 79216aed mscorsvr!GetAssemblyMDImport+0x2e1d4, calling
kernel32!RaiseException
0b79f588 799a3eb4 (MethodDesc 0x79b96470 +0xf4
System.Text.StringBuilder.Append), calling mscorsvr!Ordinal76+0x1d925
0b79f5a8 791b637b mscorsvr!Ordinal76+0x637b, calling mscorsvr!Ordinal76+0x6335
0b79f5c0 7924c8d0 mscorsvr!GetMetaDataPublicInterfaceFromInternal+0x5d70,
calling mscorsvr!GetAssemblyMDImport+0x2e16f
0b79f5f0 79996f37 (MethodDesc 0x79b96400 +0x67
System.Text.StringBuilder.ToString), calling (MethodDesc 0x79b952d0
System.String.ClearPostNullChar)
0b79f600 7924c89a mscorsvr!GetMetaDataPublicInterfaceFromInternal+0x5d3a,
calling mscorsvr!Ordinal76+0x63f8
0b79f62c 1613c135 (MethodDesc 0x14473af8 +0x3d
Microsoft.XLANGs.Core.XMessage._getMessagePropertyDefinition), calling
mscorsvr!GetMetaDataPublicInterfaceFromInternal+0x5d24
0b79f638 1613c09f (MethodDesc 0x14473b18 +0x17
Microsoft.XLANGs.Core.XMessage.GetContentProperty), calling (MethodDesc
0x14473af8 Microsoft.XLANGs.Core.XMessage._getMessagePropertyDefinition)
0b79f644 16133d6f (MethodDesc 0x14473a48 +0x37
Microsoft.XLANGs.Core.XMessage.GetPropertyValue), calling (MethodDesc
0x14473b18 Microsoft.XLANGs.Core.XMessage.GetContentProperty)
0b79f654 16133cf4 (MethodDesc 0x14473e38 +0xc
Microsoft.BizTalk.XLANGs.BTXEngine.BTXMessage.GetPropertyValue), calling
(MethodDesc 0x14473a48 Microsoft.XLANGs.Core.XMessage.GetPropertyValue)
0b79f660 16133cb4 (MethodDesc 0x15964f98 +0xdc
Microsoft.XLANGs.Core.MessageWrapperForTracking.GetPropertyValue)
0b79f674 1613bc2a (MethodDesc 0x1447c720 +0x392
Microsoft.XLANGs.Mozart.NativeInterceptor.GetPromotedProperties)
0b79f6dc 161308b0 (MethodDesc 0x1447c6b0 +0x348
Microsoft.XLANGs.Mozart.NativeInterceptor.BasicTracking), calling (MethodDesc
0x1447c720 Microsoft.XLANGs.Mozart.NativeInterceptor.GetPromotedProperties)
0b79f784 161304a9 (MethodDesc 0x1447c550 +0x41
Microsoft.XLANGs.Mozart.NativeInterceptor.TrackEventHandler), calling
(MethodDesc 0x1447c6b0
Microsoft.XLANGs.Mozart.NativeInterceptor.BasicTracking)
0b79f79c 16130125 (MethodDesc 0x14477178 +0xcd
Microsoft.XLANGs.Core.Events.FireEvent)
0b79f7fc 1448d484 (MethodDesc 0x14471d30 +0x45c
SupplyChain.BizTalk.Orchestrations.SendJDEShipConfirm.segment1), calling
(MethodDesc 0x14477178 Microsoft.XLANGs.Core.Events.FireEvent)
0b79f818 77e6bbf5 kernel32!LocalAlloc+0x63, calling
kernel32!SwitchToFiber+0x1a9
0b79f82c 77e6bbf5 kernel32!LocalAlloc+0x63, calling
kernel32!SwitchToFiber+0x1a9
0b79f830 791ca73b mscorsvr!Ordinal76+0x1a73b, calling kernel32!LocalAlloc
0b79f85c 7c820e5d ntdll!RtlQueryInformationActivationContext+0xef, calling
ntdll!RtlQueryInformationActivationContext+0x123
0b79f878 7c820e78 ntdll!RtlQueryInformationActivationContext+0x10a, calling
ntdll!RtlGetLastWin32Error+0x1a1
0b79f8c4 7c820e78 ntdll!RtlQueryInformationActivationContext+0x10a, calling
ntdll!RtlGetLastWin32Error+0x1a1
0b79f8c8 77e42b72 kernel32!QueueUserAPC+0x27, calling
ntdll!RtlQueryInformationActivationContext
0b79f8d0 7c821b54 ntdll!ZwQueueApcThread+0xc
[...shortened for brevity...]




.

Relevant Pages

  • RE: Microsoft.XLANGs.RuntimeTypes.InvalidPropertyTypeException
    ... Some time ago we found that if we enabled tracking for all elements in our ... Yes the exception is of significant concern; it is a major user error. ... the following code leaks memory: ... System.Text.StringBuilder.Append), calling mscorsvr!Ordinal76+0x1d925 ...
    (microsoft.public.biztalk.server)
  • RE: .NET Runtime 2.0 Error - I need more details...
    ... so if you can not use this event to handle the exception. ... The default event logging behavior of console application is built into ... ConsoleException.Program.Main), calling mscorwks!JIT_Throw ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework)
  • Re: Assertion on Type conversion
    ... The author states that "if a method has specified some pre-condition then the failure of that condition is the responsibility of the ... depends on the caller's ability to check for conditions, and assure them to be correct, prior to the calling of the method. ... An overlooked exception that could be handled gracefully. ... Implement a method like "IsValid" to do a runtime check first if your concerned about the ArgumentException being thrown. ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Microsoft.XLANGs.RuntimeTypes.InvalidPropertyTypeException
    ... Trying to access a data property on a message for which it has not ... Yes the exception is of significant concern; it is a major user error. ... Any exception thrown could delay the cleanup of resources, ... System.Text.StringBuilder.Append), calling mscorsvr!Ordinal76+0x1d925 ...
    (microsoft.public.biztalk.server)
  • Re: Calling a C++ DLL from a C# program. Unexpected behaviour
    ... >> 'true' every time an exception occurs. ... >> the mixed-mode debugger, ... >> calling the function. ... > public static extern bool Test(); ...
    (microsoft.public.dotnet.general)