Think that if retries are your only concern then the so
called fatal error messages would be submitted n times and
then move to suspended Q.

r
>-----Original Message-----
>Hello
>
>I'm writing AIC component (COM component in C++, MSVC71,
using ATL,
>implementing IBTSAppIntegration interface). During
processing two
>different types of error may occur:
>* non-fatal (like lost connection to database)
>* fatal (invalid document data)
>
>The problem is that I do not know how to signal to
BizTalk that fatal
>error has happend. I can only return E_FAIL (and set COM
error info to
>see more details in log), and after some time message is
processed again
>- I know how to configure retry interval and count, this
is not a
>problem. Messages with non-fatal errors should be
processed according to
>these settings. However I do not know how to signal fatal
error to
>BizTalk. Is there any special HRESULT that I can return
from
>ProcessMessage to tell to BizTalk that processed message
is invalid,
>thus disabling any futher retries of this message ? I
have found very
>little in documentation about meaning of HRESULT returned
from
>ProcessMessage ...
>
>TIA
>
>
>B.
>.
>

[ Post a follow-up to this message ]

On Fri, 27 Feb 2004 02:03:42 -0800, Ram wrote:

> Think that if retries are your only concern then the so
> called fatal error messages would be submitted n times and
> then move to suspended Q.

This is what I'm doing now, but I was hoping there is some way to move
these "permanently bad" messages to suspend queue sooner than other
messages. Thanks for reply, anyway.


B.

[ Post a follow-up to this message ]