Sequential Convoy and Long running transaction: Messages still referenced


hi everyone<o:p></o:p>

being biztalk developer since 2006, thing still stumps me.<o:p></o:p>

i have sequential convoy singleton orchestration debatches messages using rcvpipeline. orchestration needed in a fifo scenario. in order execute rcvpipeline within orchestration need encapsulate within atomic transaction scope. <o:p></o:p>

in order have atomic scope orchestration needs long running. have encapsulated atomic transaction within scope (using long running transactions) have exception handling.

<o:p></o:p>

everything works fine except 1 major detail:
when orchestration executes messages still in messagebox. can click on orchestration instance in mgmt console , @ message! tracking disabled receive port orchestration. still, messages not cleaned up.

<o:p></o:p>

i have set dta-purge 1 hour , works fine, messages still in orchestration.<o:p></o:p>

my guess long running transactions not complete (although looks should) , since transaction not completed messages not removed message box.

so, summarize: possible combine long running transactions , singleton orchestration?

//mikael sand (mcts, icc 2011) - blog logica sweden

the messages still being referenced orchestration! can make atomic transation commit?

in these cases, orchestration must complete, not specific scope.  long outer loop doesn't exit, orchestration never complete.  messages remain references forever.

note, inner atomic scope completing, otherwise, messages sent after debatching never committed messagebox.



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