|
Home > Archive > BizTalk Server Orchestration > January 2005 > endless loop
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]
|
|
| fheinema 2005-01-14, 5:49 pm |
| I have a setup where we are taking in an xml file transforming it to the same
schema with the data having been manipulated. When I submit the message I
get stuck in an endless loop and the file continues to process and write out
over and over. I am not sure how to stop it. Here is what I have for the
process.
Receive Port using the File Adapter polling a directory and bound to a
Custom Pipeline.
Custom Pipeline validates the file against the schema. Could be one of four
types of files so it validates against a 4 schema collection.
Orchestration picks up the files from the Message Box using a Direct Port.
Picking up the file is based on the message type and also a subscription
field that checks a promoted property. Orchestration is run through and the
translated file is sent through a send port using the Default XML Transmit
Pipeline and the file adapter.
The orchestration is working as planned but it continues to process and spit
out files over and over. It almost appears like the send port somehow puts
the message back in the Message Box and the orchestration picks it up again.
This never stops.
Has anyone run into this before? Does anyone have any ideas what the cause
could be and how to stop it from happenning?
--
Fred Heinemann
Frustrated Newbie
| |
| Ruslan Yakushev [MSFT] 2005-01-14, 8:46 pm |
| It looks like your orchestration picks up a copy of the message that it
publishes to the message box for sending through a send port. This is
happening because you have a direct bound orchestration.
To determine what causes the message to be routed back to orchestration you
can do the following:
1. First check what is the subscription that your orchestration creates in
the message box. Use the subscription viewer SDK tool for that.
2. Find out what are the promoted properties that the orchestration output
message has. You can do this by turning on the message tracking before the
pipeline execution in the send port, running your scenario and then going
to HAT and analyzing the context of the tracked messages.
Most probably you will have to tweak the filter expression on the
orchestration receive port so that it does not pick up its own output files.
--------------------
>Thread-Topic: endless loop
>thread-index: AcT6hWFSRur+Maw3ScuAd+FoAJlodw==
>X-WBNR-Posting-Host: 208.248.33.30
>From: "=?Utf-8?B?ZmhlaW5lbWE=?=" <fheinema@discussions.microsoft.com>
>Subject: endless loop
>Date: Fri, 14 Jan 2005 14:07:04 -0800
>Lines: 26
>Message-ID: <67845ADC-5735-431C-8D10-A3538D30F841@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.orchestration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.orchestration:9784
>X-Tomcat-NG: microsoft.public.biztalk.orchestration
>
>I have a setup where we are taking in an xml file transforming it to the
same
>schema with the data having been manipulated. When I submit the message I
>get stuck in an endless loop and the file continues to process and write
out
>over and over. I am not sure how to stop it. Here is what I have for the
>process.
>Receive Port using the File Adapter polling a directory and bound to a
>Custom Pipeline.
>Custom Pipeline validates the file against the schema. Could be one of
four
>types of files so it validates against a 4 schema collection.
>Orchestration picks up the files from the Message Box using a Direct Port.
>Picking up the file is based on the message type and also a subscription
>field that checks a promoted property. Orchestration is run through and
the
>translated file is sent through a send port using the Default XML Transmit
>Pipeline and the file adapter.
>
>The orchestration is working as planned but it continues to process and
spit
>out files over and over. It almost appears like the send port somehow
puts
>the message back in the Message Box and the orchestration picks it up
again.
>This never stops.
>
>Has anyone run into this before? Does anyone have any ideas what the
cause
>could be and how to stop it from happenning?
>
>--
>Fred Heinemann
>Frustrated Newbie
>
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
| |
| Matt Milner 2005-01-15, 2:46 am |
| WHen you send to a send port, you are publishing the message to the message
box. When it gets published, the send port id of the bound port is in the
context so that the send port is sure to get the message. However, any
subscription for that message will get the message. In other words, the
message that you send out of the orchestration cannot match the subscription
that is created by your orchestration or you will continue to loop through
new instances of the orchestration.
Matt
"fheinema" <fheinema@discussions.microsoft.com> wrote in message
news:67845ADC-5735-431C-8D10-A3538D30F841@microsoft.com...
>I have a setup where we are taking in an xml file transforming it to the
>same
> schema with the data having been manipulated. When I submit the message I
> get stuck in an endless loop and the file continues to process and write
> out
> over and over. I am not sure how to stop it. Here is what I have for the
> process.
> Receive Port using the File Adapter polling a directory and bound to a
> Custom Pipeline.
> Custom Pipeline validates the file against the schema. Could be one of
> four
> types of files so it validates against a 4 schema collection.
> Orchestration picks up the files from the Message Box using a Direct Port.
> Picking up the file is based on the message type and also a subscription
> field that checks a promoted property. Orchestration is run through and
> the
> translated file is sent through a send port using the Default XML Transmit
> Pipeline and the file adapter.
>
> The orchestration is working as planned but it continues to process and
> spit
> out files over and over. It almost appears like the send port somehow
> puts
> the message back in the Message Box and the orchestration picks it up
> again.
> This never stops.
>
> Has anyone run into this before? Does anyone have any ideas what the
> cause
> could be and how to stop it from happenning?
>
> --
> Fred Heinemann
> Frustrated Newbie
|
|
|
|
|