|
Home > Archive > BizTalk Server Orchestration > January 2005 > Strange behaviour after correlation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Strange behaviour after correlation
|
|
|
| Hi,
I have noticed a strange behaviour in our orchestration after a message is
received from a third-party. The message is correlated properly with the
orchestration instance (due to the fact that the third party receives a
success response from the Biztalk HTTP adapter).
However, after this the next steps in the orchestration are not executed at
all. When I open the HAT, I see that the status of the orchestration instance
has changed from "Dehydrated" to "Active", but nothing happens. Also, when I
choose "Service Details" for this orchestration instance, I get a list of
messages - one of them is of type
"Microsoft.BizTalk.XLANGs.BTXEngine.BTXTimerMessage" with status "Delivered,
not consumed".
Can someone please explain how to handle this behaviour. This is happening
randomly for some instances of the same orchestration, but the rest work fine.
Thanks
| |
| Silly_King 2005-01-13, 5:51 pm |
| I've run into a similar issue... do you use any scopes in your orchestration?
if yes, are they transactional? If you suspend the orchestration, and then
resume it, does the orchestration continue normally?
"Ea" wrote:
> Hi,
>
> I have noticed a strange behaviour in our orchestration after a message is
> received from a third-party. The message is correlated properly with the
> orchestration instance (due to the fact that the third party receives a
> success response from the Biztalk HTTP adapter).
>
> However, after this the next steps in the orchestration are not executed at
> all. When I open the HAT, I see that the status of the orchestration instance
> has changed from "Dehydrated" to "Active", but nothing happens. Also, when I
> choose "Service Details" for this orchestration instance, I get a list of
> messages - one of them is of type
> "Microsoft.BizTalk.XLANGs.BTXEngine.BTXTimerMessage" with status "Delivered,
> not consumed".
>
> Can someone please explain how to handle this behaviour. This is happening
> randomly for some instances of the same orchestration, but the rest work fine.
>
> Thanks
|
|
|
|
|