Forum main
page
Most
active member
Login page
Register
Log out
Search page
Information Online
View our event calendar
Add general event such as an upcoming
software release or conference
View all birthdays
Public image gallery
Upload your images in your profile
Profile editing page
Subscription list page
Address book page
Member list page
View the
most active member
User groups listing
Private message page
|
|
Users viewing this topic: none
|
|
Login | |
|
failed message routing to a folder. - 21 March 2008
|
|
|
naresh_p123
Posts: 3
Score: 0 Joined: 21 March 2008 Status: offline
|
hi this is my first post .please help me on this issue. i have 3 orchestrations among which 3 rd orchestration is used to subscribe for failed messages. i am validating an xml file in the first orchestration using xmlreceive pipeline.which on failure it results as failed message. and i am using filter to get that message in 3 rd orchestration.but in third orchestration i had created one dynamic send port (which is used to send the failed message using file adapter to a folder ). everything works fine as message goes as failed->then 3 orch subscribes.and it get's the message.but when it is moving the failed message to a folder it is throwing up following Xlang's error in the eventlog. eventId:10034 Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'ABBEDPV100.ErrorHandler(19ac7812-38bf-0cb0-aafc-720c0a40b1f7)'. The service instance will remain suspended until administratively resumed or terminated. If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception. InstanceId: a2a27804-ddb3-4834-b8d1-544728313c0a Shape name: SendErrorMessage ShapeId: 83b61bbb-0ad2-4a56-be41-dcd3dda73d01 Exception thrown from: segment 3, progress 26 Inner exception: Type 'System.Management.ManagementObjectSearcher' in Assembly 'System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable. Exception type: SerializationException Source: mscorlib Target Site: System.Reflection.MemberInfo[] InternalGetSerializableMembers(System.RuntimeType) The following is a stack trace that identifies the location where the exception occured 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(Type objectType, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Type objectType, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter) 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.ServiceContext.PendingCommit(Boolean ignore, XMessage msg) at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg) at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg) at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, Context cxt, Segment seg, ActivityFlags flags) at ABBEDPV100.ErrorHandler.segment3(StopConditions stopOn) at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp) For more information, see Help and Support Center at and i had marked all the calsses as [Serializable] in my application. and i dont know why it is still throwing serialization error..? please help me on this issue, thanks a lot in advance. Naresh
_____________________________
naresh
|
|
|
|
RE: failed message routing to a folder. - 21 March 2008
|
|
|
naresh_p123
Posts: 3
Score: 0 Joined: 21 March 2008 Status: offline
|
hi now i made 3rd orchestration properties transaction type as atomic. and now am able to get rid of that error.(serialization) but the failed message is not moved into the folder..? what should i do to pass that failed xml message(input.xml file) to a folder..?
_____________________________
naresh
|
|
|
|
RE: failed message routing to a folder. - 25 March 2008
|
|
|
JohnD
Posts: 141
Score: 0 Joined: 13 April 2004 Status: offline
|
Naresh, a couple of points. If you mark a class as serializable, you are obliged to implementat the serialization interface. Do something simple, but the idea is that BizTalk wants to save any state in the object and restore it when the orchestration comes back to life. If your object has no state, then leave the method empty. You should only use the atomic scope if that's what you really want. It's basically a way to engage in the a classic Microsot transaction (with the DTC). So, if you aren't interested intransactions then don't use it. I'm guessing you are trying to declare a scope and getting the message about "this object needs to be serializable". It's reasonable because simple scopes cause BizTalk to svae out the state. So, go back to your original attempt and make sure the object is serializable. If you really want the atomic transaction, then be careful - when something fails in the scope, everything is rolled back. So you don't see any intermediate results. John D.
|
|
|
|
RE: failed message routing to a folder. - 25 March 2008
|
|
|
naresh_p123
Posts: 3
Score: 0 Joined: 21 March 2008 Status: offline
|
Hi john thanks for your repley.yes your guess is right .i am declaring a scope. yes i want to go back to previous attempt as transaction type =none.since it worked earlier all of sudden it given this issue..i am not sure which setting has gone wrong. but where do i check which one i need to make serializable. since all the C# classes which i am calling in biztalk are marked as [Serialize] attribute. that to it is throwing the system.management.dll is not serialize....i think it is somthing to do with the methods related to system.management ,which i am accessing. but how can i find which one is it.... and also when i use the atomic transaction everything works fine but it is commiting(sending the failed message to folder) after completion of entire process..which i dont want... please help me out...
|
|
|
|
RE: failed message routing to a folder. - 25 March 2008
|
|
|
JohnD
Posts: 141
Score: 0 Joined: 13 April 2004 Status: offline
|
Naresh, I guess you are calling out to your class, and it calls out to others, including something in system.management. If you can't tell from the stack trace, then you can find out where the problem is either (a) by putting some trace calls into your code, or (b) by using the debugger. If you use tracing, then just call out to System.Diagnostics... If you want to debug, then attach to the BizTalk process from inside Visual Studio (btsntsvc.exe). But I expect the problem is that you have marked the class as serializable but you haven't implemented ISerializable. John D.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|