|
Home > Archive > BizTalk Server Orchestration > July 2005 > Correlation subscription happening only once
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 |
Correlation subscription happening only once
|
|
| Jason Agostoni 2005-07-26, 5:53 pm |
| Short version:
Can anyone think of a reason why correlation subscription matching
would happen only once for an orchestration?
Long Version:
I have one orchestration calling another orchestration (using Start
Orchestration and a Direct port to sync). A correlation set is
initialized on the activate of the first (parent) orchestration and
passed into the second orchestration. That orchestration waits for
another message (of another type) that is correlated with the first
message.
The first time I run through this orchestration, everything works
great. Using the subscription viewer I can see the XLANG correlation
getting created after I drop the first message. Once I drop the second
message it gets matched and the set dissapears and everything looks
back to normal. However, if I try another test the correlation set does
NOT get initialized (as see in the subscription viewer). If I restart
teh BizTalk service. I can run through it again.
Weird?
Thanks,
Jason
| |
| Jason Agostoni 2005-07-27, 8:47 pm |
| Update:
Ok ... so after stuggling for hours, here is what I came up with ...
maybe it has something to do with me using a VPC for my BT dev:
First time through, the Main orchestration and child orch are
immediately dehydrated (not that it should matter). The second time
through, they stay active. I let it sit for a long time (while I was
eating  ) and when I came back they had dehydrated. Now everything
seems to work just fine.
So ... the fact is I have no idea what or why but at least I might have
a workaround?
Jason Agostoni
..Net Architect
CEI (www.ceiamerica.com)
http://jason.agostoni.net
Jason Agostoni
|
|
|
|
|