|
Home > Archive > BizTalk Server General > August 2005 > "Large" Messages
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]
|
|
| Bakunin 2005-08-30, 8:02 am |
| Hi,
I have read quite a few comments, including the excellent blog from
http://blogs.msdn.com/biztalk_core_.../28/381700.aspx
on large file sizes processed using Biztalk 2004. The scenarios detailed in
the blog above unfortunately do not really describe the scenario I have.
Basically I have an XML message with a (base 64 encoded) document attached.
We basically the file, writing any structured details to a DB and the
document to a document repository. The whole message can be up to 10MB in
size (we have set the limit using config).
However during testing when we dumped between 5 and 10 messages that were
about 10MB each we starting getting "Out Of Memory Errors" among other
things.
My question or observation is that 10MB is not >>that<< big, is it? What
would cause this to log an Out of Memory error on a machine with 1.5 GB of
memory. CPU usage did rocket and stayed at close to 100% for a number of
minutes. Out of the 10 messages 5 were processed.
I thought I had read that people had successfully sent messages much larger
than this.
Any comments greatly appreciated
| |
| Stephen W. Thomas 2005-08-30, 5:58 pm |
| Hello.
It seems like you are overloading the system even though that load may seem
relatively small. When messages arrive into biztalk, they can grow many
times there size depending type, mapping, orchestration use etc. I was able
to crash biztalk with a single large message because I was making too many
copies of it inside an Orchestration.
Here are a few suggestions that might help:
- Make sure you are running SP1
- Create multiple host for receiving, processing, and sending
- Try to adjust the server setting to slow down processing on the area that
seems to have the problem. i.e. if your orchestration are crashing scale
them back or scale back the receiving water marks.
This tool can help:
http://download.microsoft.com/downl...ss_Settings.EXE
Make sure you know what each setting does before you change them.
That’s about all I can think of without add additional resources to scale
the hosts as needed or break up the file into smaller pieces.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
http://geekswithblogs.net/sthomas/
"Bakunin" wrote:
> Hi,
> I have read quite a few comments, including the excellent blog from
>
> http://blogs.msdn.com/biztalk_core_.../28/381700.aspx
>
> on large file sizes processed using Biztalk 2004. The scenarios detailed in
> the blog above unfortunately do not really describe the scenario I have.
> Basically I have an XML message with a (base 64 encoded) document attached.
> We basically the file, writing any structured details to a DB and the
> document to a document repository. The whole message can be up to 10MB in
> size (we have set the limit using config).
> However during testing when we dumped between 5 and 10 messages that were
> about 10MB each we starting getting "Out Of Memory Errors" among other
> things.
>
> My question or observation is that 10MB is not >>that<< big, is it? What
> would cause this to log an Out of Memory error on a machine with 1.5 GB of
> memory. CPU usage did rocket and stayed at close to 100% for a number of
> minutes. Out of the 10 messages 5 were processed.
>
> I thought I had read that people had successfully sent messages much larger
> than this.
> Any comments greatly appreciated
|
|
|
|
|