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.
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
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