Re: Maxed CPU on file adapter xml receive pipeline

From: Xerox (info_at_thinkscape.com)
Date: 03/11/05 

Date: Fri, 11 Mar 2005 16:57:34 -0000

Blush. I have brought shame to the BizTalk family! It sounds really stupid
but it was an honest mistake to make (in my own mind anyway):

It works out that the xml receive adapter is working very well. Very fast in
fact. The problem boiled down to setting a distinguished field with the
content of an xml document. I use this technique a lot and have not had a
problem with it. What I didn't realise, is that distinguised fields get
carried along with a message's context. I only thought that applied to
promoted properties. So what was happening is, that the entire xml content
was being pushed in to the message's context!!! 20mb worth of it!

So with a very red face, I "undistinguised" my fields and use an xpath
statement to set then instead. This has improved the situation enourmously!

Let that be a lesson to anyone else as daft as me.

"Xerox" <info@thinkscape.com> wrote in message
news:OW#90ojJFHA.1176@TK2MSFTNGP12.phx.gbl...
> I have looked back through the newsgroup history and have seen references
to
> others suffering from maxed CPU and eventually having to terminate BizTalk
> process on receiving XML files in a file adapter. Unfortunately there is
no
> conclusion that I could draw from it on what the resolution is.
>
> The file is a 20mb xml file with about 100,000 records in (the structure
is
> fairly flat). After 20 minutes BizTalk still hadn't passed the message on
to
> the orchestration so I forcibly stopped it.
>
> This was really surprising as I have processed flat files using the flat
> file pipeline component with over 400,000 record in it within a few
minutes.
> With XML inflation, they were in the order of 80mb in size. Worked fine!
>
> I have not applied service pack 1 for BizTalk yet, which I am about to
do -
> hopefully it will cure the problem. But if not, then what gives? Why does
> flat file parser work but xml receive doesn't? Its going to be a backward
> step if I have to rework systems to send data in flat files because
BizTalk
> chokes on relatively small 20mb files!
>
>

Relevant Pages

  • Re: SISS vs Biztalk Large data
    ... I am too using SSIS instead of BizTalk to Process Large XML and Flat Files ...
    (microsoft.public.sqlserver.dts)
  • Re: Receiving messages via http
    ... > You'll probably want to use the FTP adapter for that, or a web service ... >> data from XML and flat files but I am looking to receive data ... is there any way that BizTalk can access a remote ...
    (microsoft.public.biztalk.general)
  • Receiving messages via http
    ... data from XML and flat files (CSV etc) but I am looking to receive data via ... is there any way that BizTalk can access a remote XML ...
    (microsoft.public.biztalk.general)
  • Re: Maxed CPU on file adapter xml receive pipeline
    ... > others suffering from maxed CPU and eventually having to terminate BizTalk ... > This was really surprising as I have processed flat files using the flat ... > With XML inflation, they were in the order of 80mb in size. ...
    (microsoft.public.biztalk.general)
  • RE: .NET objects (C#)
    ... and BizTalk Receive and Send handlers treat all message content ... Adapters can pass any content in - it doesn't have to be XML. ... say, the File adapter, and select Pass-through pipelines (pipelines that ... message received by the orchestration, BizTalk will at this stage attempt XML ...
    (microsoft.public.biztalk.general)