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

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

hi , background: for our customer, having a  2 biztalk , 1 sql setup of environment. [biztalk server 2013 azure vms provisioned azure gallery, sql server 2012 azure vm ]. in current configuration, there no high availability or disaster recovery plan set. want implement dr , possibly ha configuration on these servers. i have few questions regarding same. please let me know thoughts on same. currently writing log files (log shipping files) mounted/attached drive same sql server. how move these log files across secondary site since shared storage not supported. in case of sql server crash, losing log files since reside on same server. please share options on how can move these periodically between datacenters. for hosts pop3, ftp need host clustering (which requires biztalk machines present on windows cluster traditionally), please let know how achieve in azure scenario thanks , regards, ujjwal devarapalli -ujjwal you can refer article, issue azure vm lo...
Read more

How to send non-standard Content-Type header ?

hello, my custom client developed send custom content-type header "xyz" (with out "/"). message gone in lcs 2005. after have upgrade lcs 2005 ocs 2007 r2 in test environment. custom client not able send same custom content-type in ocs 2007 r2 used possible send in lcs 2005. below cut ocs 2007 r2 accessedge log file. tl_warn(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de7 (sipstack,ccontenttypeheader::parse:contenttypeheader.cpp(118))( 00000000036249f0 ) exit - media-type syntax error in getting "/" tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de8 (sipstack,csipmessage::parseallheaders:sipmessage.cpp(6408))( 0000000003566a50 ) exit. failed while parsing header. tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de9 (sipstack,csiprequest::validateinboundheaders:siprequest.cpp(1391))( 0000000003566a50 ) exit - failed while parsing header. returned 0xc3e93f51(sipproxy_e_invalid_content_type_header)...
Read more