Hi,

in one of my Orchestrations I'm using the "Call Orchestration" shape. It's
getting called approximately 500 times a day. Unfortunately sometimes the
called Orchestration is executed twice. This is happening once or maybe twic
e
a day, but there are other days where it doesn't happen at all.

In the HAT I can see that the called Orchestration was completed
successfully. No error was thrown and I can't see any other entry that is
indicating a problem.

I have put some trace points in both Orchestrations and have seen that the
message which is used as the input message is correct. In the called
Orchestration the incoming message is correct as well and therefore it
completes successfully.
But a few milliseconds later the same Orchestration with exactly the same
input message is executed again and I have no idea why this is happening.

To me it's curios since there is no retry count which I can set for the
"Call Orchestration" shape and I don't think that it is trying to execute
again if an error occurs within the called Orchestration (which isn't the
case here, both times the called Orchestration is doing all the work that it
should do)

Does anyone has noticed a similar behaviour or has any idea what else I
could try ?

Thanks.
Thorsten

[ Post a follow-up to this message ]

Hello Thorsten,

Do you have a transaction in your orchestration with retry set to true?


BA
http://biztalkia.blogspot.com/

> Hi,
>
> in one of my Orchestrations I'm using the "Call Orchestration" shape.
> It's getting called approximately 500 times a day. Unfortunately
> sometimes the called Orchestration is executed twice. This is
> happening once or maybe twice a day, but there are other days where it
> doesn't happen at all.
>
> In the HAT I can see that the called Orchestration was completed
> successfully. No error was thrown and I can't see any other entry that
> is indicating a problem.
>
> I have put some trace points in both Orchestrations and have seen that
> the
> message which is used as the input message is correct. In the called
> Orchestration the incoming message is correct as well and therefore it
> completes successfully.
> But a few milliseconds later the same Orchestration with exactly the
> same
> input message is executed again and I have no idea why this is
> happening.
> To me it's curios since there is no retry count which I can set for
> the "Call Orchestration" shape and I don't think that it is trying to
> execute again if an error occurs within the called Orchestration
> (which isn't the case here, both times the called Orchestration is
> doing all the work that it should do)
>
> Does anyone has noticed a similar behaviour or has any idea what else
> I could try ?
>
> Thanks.
> Thorsten

[ Post a follow-up to this message ]

Hello,

no, the Orchestration and the scope from where the Orchestration is called
have both Long-Running transactions, but no Atomic Transaction with a retry
is used.

Thanks.
Thorsten

"BA" wrote:

> Hello Thorsten,
>
> Do you have a transaction in your orchestration with retry set to true?
>
>
> BA
> http://biztalkia.blogspot.com/
> 
>
>
>

[ Post a follow-up to this message ]

Does anyone has other comments, solutions in mind ?

Thanks.
Thorsten

"Thorsten Schilz" wrote:
[vbcol=seagreen]
> Hello,
>
> no, the Orchestration and the scope from where the Orchestration is called
> have both Long-Running transactions, but no Atomic Transaction with a retr
y
> is used.
>
> Thanks.
> Thorsten
>
> "BA" wrote:
> 

[ Post a follow-up to this message ]