RE: help with serialization error in Orchestration


Please see the following exception information. The exception is cause by a
send shape in the middle of the Orchestration.

I believe it's cause by the correlation set I tried to initialize in the
send message. The message gets sent out by the send shape is created in the
orchestration and the correlation set has one GUID property. I need the GUID
in the following receive shape and the received message.

What I don't understand is why it's a problem to serialize the message in
the messagebox. How can I get around the error and initialize the
correlation set in the message.

PS, I have a property schema for the message, and only one field in the
property schema I assigned to correlation set.



FYI, the exception message is

Type 'System.Xml.XmlDocument' in Assembly ... is not marked as serializable.

StackTrace Information

*********************************************

at
System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType
type)

at
System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type
type, StreamingContext context)

at
System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()

at
System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object
obj, ISurrogateSelector surrogateSelector, StreamingContext context,
SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter,
ObjectWriter objectWriter)

at
System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object
obj, ISurrogateSelector surrogateSelector, StreamingContext context,
SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter,
ObjectWriter objectWriter)

at
System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo
objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)

at
System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object
graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)

at
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream
serializationStream, Object graph, Header[] headers, Boolean fCheck)

at Microsoft.XLANGs.Core.ObjectSerializer._serialize(Object graph,
StringLookup sl)

at
Microsoft.XLANGs.Core.ObjectSerializer.SerializeStateManager(IStateManager
stateMgr, StringLookup lookup)

at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx,
Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean
terminate)

at Microsoft.XLANGs.Core.LongRunningTransaction.PendingCommit(Boolean
ignore, XMessage msg)

at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32
iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[]
followCorrelations, Context cxt, Segment seg, ActivityFlags flags)

at MyTest.MyLoadOrchNew.segment2(StopConditions stopOn)

at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s,
StopConditions stopCond, Exception& exp)

Any help?

Thanks.

-fj


Hi,

I have the same problem. There might be one of 2 issues: it could be the correlation setting (we use MQSeries.dll and set de MQ_MD_CorrelId property) but that is sometimes going ok, then again it fails.

Another problem might be that we use a custom .Net component to read configuration files. Some have found that if you only use component initialisation in Atomic Transactions (meaning EVERY orch you use should at least be longrunning transactions set) this would eliminate this error.

Is there anything in your situation that might go along with that?

BizTalk Utilities - Frustration free BizTalk Adapters
http://www.topxml.com/biztalkutilities
.

Loading