Resuming messages vs. orchestrations


we shop new biztalk 2006 r2.  our first application seems simple not behaving expected in circumstances.

the orchestration simple.  message received; transformation takes place; message sent external web services; log record written.  our problem occurs when external web service not reply.  biztalk makes 3 attempts , suspends orchestration/message (as should).

in admin console see suspended message , suspended orchestration.  both marked resumable.  attempts resume orchestration fail.  can resume message.  however, resuming message seems complete send; log record not written.  once resumed message completes, have terminate suspended orchestration rid of it.

1.  observation, appears resuming message completes activity (shape) suspended.  true?

2.  relationship between suspended message , suspended orchestration?  had thought resuming orchestration pick suspended message.  not seem case.

i have looked around on web; in forum; , in books have.  can't find explains above behavior.  or pointer explanatory resources appreciated.

1- messages suspended due transmission/receive failure or in execution of pipeline. therefore if resuming message means retry send message failed (in pipeline or transmission through adapter).

2- if orchestration suspended , resume it, resume last persisted state. biztalk runtime makes persistent points during execution of orchestration , depends on scope of transactions , other shapes (send/receive etc.) within orchestration.

thanks
abdul rafay http://abdulrafaysbiztalk.wordpress.com/ please mark answer if helps


BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more