August 2, 2006 at 5:27 AM #14101
If I remember correctly, I think there is a problem with the Delay shape inside a Listen if you set a variable for the time. Or something like that. You might want o check on delays that are working and make sure they are the same.
I’m not sure if having a scope on the Receive Shapes will do you much – but probably not causing a problems.
You seem to have a lot of scopes. Are any Atomic? Those can mess up Timeouts.
That’s about all I can think off the top of my head.
August 2, 2006 at 4:42 AM #14102
Im facing a problem with delay in orchestrations.
Im building the solution that has a backbone orchestration calling a few other orcs in parallel.
Now each orc called has a orc level scope and a scope enclosing my send receive shapes i.e two scopes.
In the inner scope i have a listen branch with two receive and a delay.
I set the delay parameter after the message has been sent and just before the listen brach.On a timeout i have to re-send the message.
But im am experiencing a weird behaviour.
The first time i start the biztalk service there is an immediate timeout i.e no wait irespective of the timeout value.
On subsequent runs i do get a timeout but not an exact one.It timeouts out before the specified timeout or the orc just dehydrates.
I have tried solutions like hard coding the time out value changing the transaction type of the orc to LONG Running but nothing seems to work.
This is a serious problem and will appreciate any responses from your side.
In case the solution is too descriptive to be posted kindly mail it to email@example.com.
Will appreacite any kind of help.
Thanks And Regards,
August 16, 2006 at 5:53 AM #14103
we have fixed the problem by installing he biztalk service pack -1
this service pack renders to fixing the delay problem.
i thank all for atleast viewing the problem.
Thanks a lot…… 😆
August 3, 2006 at 10:09 AM #14100
We have tried hard coding the value of the delay without any success.
Also the scopes are for highly granular exception handling none of them are atomic or even long running.
Am i violating the biztalk standards by using delay in multiple orcs called simultaneouly from the backbone orc.Cause i see the backbone orc to be dehydrated as whole when the orc is giving such weird behaviour.
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.