BizTalk - Non-repeatable BizTalk issue in PROD
Asked By Robert Song
10-Aug-11 12:07 AM
Hi,
There is an issue in prod BizTalk servers(two servers load balance) that happened occasionally in prod, however it is not re-produced. Senario as below:
1. In Orch1, call Business rule. if rule meet the condition, call .net component to add error message to .net list object
2. At the end of Orch1, to check count in the .net error message list object. if count>0, copy the list object to xml message(envelope message with multiple single message nodes in xml)
3. send the envelop message from Orch1 to Orch2, which has xml disamble pipeline to split envelop to single ones. Orch2 has one receive port and sent port. (send port in Orch1 and receive port in Orch2 for envelope message share same location binding
What is happening is periodically the final output of single split message was not there when it should be there(for sure the Business rule met the condition). I have achieve folder to save all dropped initial files. After I redropped the same initial file from beginning, everything works again.
Q: How to debug/capture it when the orch/port not working properly?
Thanks a lot
Vickey F replied to Robert Song
The following screenshot shows a typical debugging session in the Orchestration Debugger.
The Orchestration Debugger consists of three panes that are always present and two optional panes that appear when attached to an orchestration instance:
- The Service pane displays the instance service name and GUID that uniquely identifies the orchestration instance, debug mode, orchestration state, whether the Orchestration Debugger is attached, and service options.
- The Tracked Events pane lists the status of every action performed in the orchestration, such as whether it started or completed. As you select each of the rows in this pane, the corresponding shape in the Orchestration pane appears highlighted in green when the shape starts and blue when the shape finishes.
- The Orchestration pane is where a visual representation of the orchestration is rendered with all of its shapes.
- The Variable List pane appears when attached to an orchestration instance and displays the name, value, and type of the variable. The value indicates if the variable is null or, if not, then what kind of object it contains. Type is the Assembly.Namespace.Name of the object.
- The Variable Properties pane appears when attached to an orchestration instance and displays properties for the variable that vary according to the type of object. For example, for messages this includes Message Parts (including Name, Properties, Size, Type, and Value) and Message Properties (including Context, Name, PartCount, Scope, Type, and Value).
Follow this link-
http://msdn.microsoft.com/en-us/library/aa953746%28v=bts.20%29.aspx
Hope this will help you.
Robert Song replied to Vickey F
Thanks for the reply. I knew the steps you posted for orch debugging. The problem is the issue doesn't happen all the time. Just like in my original post, when I tried to re-drop same incoming xml for Orch1, all the steps works perfectly.
Robert Song replied to Robert Song
It still keeps as unresolved issue. Reason behind the sink could be .net method invoking between BRE and Orchestration, the instance of custom class got mixed up or missing occasionally. Does anybody have advice what the best practice to using .net class? Doe BizTalk automatically make same instance calling of .net class within life cycle of the class object when messages be processed parallely?
Robert Song replied to Vickey F
The
Xml.Serialization was used in my help class. The list object was returned by .net method call in Orchestration to be serialized to xml document. Anybody know this could cause random issue? No any exception or error can be found when issue happened. So wired!!!
BizTalk 2006 - - intermittent crash and restart Windows Server Hi all. . . My BizTalk host instance is occasionally recycling with the familiar Specifically, Event ID 5410 - -- - An error occurred that requires the BizTalk service to terminate. The most common causes are the following: 1) An unexpected out of OR 2) An inability to connect or a loss of connectivity to one of the BizTalk databases. The service will shutdown and auto-restart in 1 minute. If the problematic database remains unavailable, this cycle will repeat. Error message: Exception has been thrown by the target of an invocation. Error source: mscorlib BizTalk host name: BizTalkPricingApplication Windows service name: BTSSvc$BizTalkPricingApplication For more information, see Help and Support Center at http: / / go.microsoft.com / fwlink / events.asp. - -- - True to its word, the BizTalk host instance shuts down and restarts. Looking at HAT, I can see that the error
BizTalk - - error after being idle, loading AppDomain Windows Server Hi all. . . I've noticed that when our BizTalk system is idle for more than half an hour or so, the next time a message comes in, the orchestration fails to load, and I get an error saying that BizTalk needs to restart. After the restart, though, the orchestration picks up the message and processing The only information in the error log is this: - -- -- -- -- -- -- -- -- An error occurred that requires the BizTalk service to terminate. The most common causes are the following: 1) An unexpected out of OR 2) An inability to connect or a loss of connectivity to one of the BizTalk databases. The service will shutdown and auto-restart in 1 minute. If the problematic database remains unavailable, this cycle will repeat. Error message: Exception has been thrown by the target of an invocation. Error source: mscorlib BizTalk host name: BizTalkPricingApplication Windows service name: BTSSvc$BizTalkPricingApplication - -- -- -- -- -- -- -- - What I've discovered is that if
30-90 seconds Windows Server Our SQL Server runs on a different server than the BizTalk server. Occasionally BizTalk loses connection to the SQL Server. it happens frequently but reconnects 60-90 seconds later. The errors all point to BizTalk processes running when the connection is lost and our Orchestrations do not directly interact with SQL Server. In other words, we do not access the databases but any internal BizTalk function that may be called as an indirect action may access the database. Some of of the errors thrown in the event logs. Note: These are only occuring on the BizTalk server, no errors can be found on the SQL Server. Warning: a couple of these bts_GetDynamicStateInfo_prpsIntS2BizTalkServerApplication]( ?, ?, ?)}". SQL Server returned error string: "Connection failure". = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Failed while creating a mil_af_prps_INTS2_PRPSOrchestrations.mil_af_prps_INTS2_CIDSShowProcurementHistory service. Exception type: ServiceCreationException Source: Target Site: Help Link: The following is a stack trace that identifies the location where the exception occured at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession._serviceCreator(Guid&, Object) at Microsoft.XLANGs.Core.ResourceContainer._allocateResource(Guid&, UInt32, ResourceCreator
XLANG throws an exception while trying to log an exception to the Event Log Windows Server The original message is getting lost so I have 2) Is it possible to get this this issue resolved? 3) Once this happens the cycle repeats itself over and over again until I suspend the orchestration. Unexpected exception (see the 'inner exception' below) has occurred while executing an instance of service 'Company.Namespace.Here(b6a1f702-ceb5-170f InstanceId: 47ea3dc6-f7bf-4223-90c3-82b6640a4737 Shape name: LogCompletion ShapeId: ff83c316-6cb8-4ab4-be70-49365b7dee00 Exception thrown from: segment 1, progress 78 Inner exception: Log entry string is too long. A string written to the event log cannot exceed 32766 characters. Exception type: ArgumentException Source: System Target Site: Void InternalWriteEvent(UInt32, UInt16, System.Diagnostics.EventLogEntryType, System.String