|
Home > Archive > BizTalk Server General > November 2004 > Correlating on File.ReceivedFileName
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 |
Correlating on File.ReceivedFileName
|
|
| Muhammad Omer [Xavor] 2004-11-11, 7:46 am |
| I have a situation where I need to correlate an incomming message to an
outgoign message.
I've declared a correlation type with the property File.ReceivedFileName.
While initializing my correlation set, I set the File.ReceivedFileName of my
outgoing message to what I expect as the filename of the response.
I run the sample but the response message does not end up with the
orchestration (I get a delivery failure), one stuck orchestration and a
suspended message.
I have checked the ReceivedFileName property of the stuck message from HAT
and compared it to the subscription setup for the waiting orchestration
(from teh subscription viewer) and they match perfectly. I have even
promoted ReceivedFileName using a custom pipeline but the message does not
seem to get routed to the orchestration instance.
Any ideas what I might be doing wrong?
Omer
| |
| Stephen W. Thomas 2004-11-11, 7:46 am |
| Just wanted to check to make sure you are following that correlation set on
the Receive after you Send the message? I would guess it wouldn’t compile
otherwise….
Maybe in the suspended message, double check to make sure the
File.ReceivedFileName has isPromoted = true. If not, it would be a problem
and not get routed. Although, it sounds like you have already taken care of
that with the custom pipeline.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"Muhammad Omer [Xavor]" wrote:
> I have a situation where I need to correlate an incomming message to an
> outgoign message.
> I've declared a correlation type with the property File.ReceivedFileName.
> While initializing my correlation set, I set the File.ReceivedFileName of my
> outgoing message to what I expect as the filename of the response.
> I run the sample but the response message does not end up with the
> orchestration (I get a delivery failure), one stuck orchestration and a
> suspended message.
> I have checked the ReceivedFileName property of the stuck message from HAT
> and compared it to the subscription setup for the waiting orchestration
> (from teh subscription viewer) and they match perfectly. I have even
> promoted ReceivedFileName using a custom pipeline but the message does not
> seem to get routed to the orchestration instance.
> Any ideas what I might be doing wrong?
> Omer
>
>
>
| |
| larry franks 2004-11-11, 5:49 pm |
| Ok, so we initialize the correlation set, is your receive set to follow the
correlation set? It sounds like this should be working for you. Can you
post your project?
Larry Franks
This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: "Muhammad Omer [Xavor]" <XavorDotNet@nospam.nospam>
| Subject: Correlating on File.ReceivedFileName
| Date: Thu, 11 Nov 2004 15:00:07 +0500
| Lines: 17
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.181
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
| Message-ID: <OkC3yU9xEHA.748@TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: lhr63.pie.net.pk 202.125.140.214
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:21538
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| I have a situation where I need to correlate an incomming message to an
| outgoign message.
| I've declared a correlation type with the property File.ReceivedFileName.
| While initializing my correlation set, I set the File.ReceivedFileName of
my
| outgoing message to what I expect as the filename of the response.
| I run the sample but the response message does not end up with the
| orchestration (I get a delivery failure), one stuck orchestration and a
| suspended message.
| I have checked the ReceivedFileName property of the stuck message from HAT
| and compared it to the subscription setup for the waiting orchestration
| (from teh subscription viewer) and they match perfectly. I have even
| promoted ReceivedFileName using a custom pipeline but the message does not
| seem to get routed to the orchestration instance.
| Any ideas what I might be doing wrong?
| Omer
|
|
|
|
|
|
|
|