What I did:
Scope: windows server 2003 +SP2 , 2 CPU, 4G memory.
2288 flat files copied to listening folder, just with mapper and send
****t,
no orch.
1. Change SQL Service 2005 Query timeout to 10 minutes
2. Installed .Net 2.0 SP1
3. Add /3G switch
4. Disable Biztalk DW Re****t ( regedit)
5. Disable Biztalk "EnableTracking" (regedit)
6. Uncheck compile optimization
7. Make sure external assembly( C# referenced by mapper) is thread safe.
result:
1. 2288 files, two crashes occured on Biztalk application.
2. 2 " memory corrupted" errors
3. 1 Zombie 0xC0C01B4C error caused sending file in looping. ( Biztalk
bug?)
Since memory usage < 2.5G, I don't think it is memory capacity problem.
What I doubt are :
1. Internal Thread safe problem in C# 2.0
2. SQL Server 2005/ Agent / DTC crash on heavy load.
The following function throwed error:
public static string ConvDate1(string p_strParm0)
{
if ( p_strParm0==null) return "";
int length = p_strParm0.Length;
string sDate="";
switch (length)
{
case 10: //yyyy/mm/dd--> mm/dd/yyyy
char sep = '-';
if ( p_strParm0.IndexOf("/")>0) sep = '/';
string[] ArrDate = new string[3];
ArrDate= p_strParm0.Split(new char[]{sep},3);
if ( ArrDate.Length==3)
sDate = ArrDate[1] + "/" + ArrDate[2] + "/" +
ArrDate[0];
break;
case 8://yyyymmdd->mm/dd/yyyy
sDate = p_strParm0.Substring(4, 2) + "/" +
p_strParm0.Substring(6) + "/" + p_strParm0.Substring(0, 4);
break;
default:
sDate = p_strParm0;
break;
}
return sDate;
}
"Neil" wrote:
> Sounds like you are running out of memory, have you got a new Host for
the
> Send, Receive and Processing (Orchestration) for that Application ?.
Monitor
> the BTS using Perfmon (Processes, Working Set) to see if you are
bleeding
> memory.
>
> Remove all of the custom components and then add them back in one at a
time.
>
> - Don’t try to tune the Host UNTIL After you have done this!
>
> When you tune it, drop the number of messages being processed by the
send
> ****ts right down (1/2) then retry, if that fixes it then the messages
are to
> big (It loads based on Processor, Core etc). There is a good but
complex
> article on the MSDN about this.
>
> Don’t try and change to much at once.
>
>
>
> N
>
>
> "Q1andQ2" wrote:
>
> > if '0x00' comes without cra****ng, it throws the event of " Attempted
to read
> > or write
> > protected memory. This is often an indication that other memory is
corrupt".
> > After a while, the machine crashed.
> >
> > "Eric Stott" wrote:
> >
> > > Lets leave the swearing to other forums.
> > >
> > > Do you experience the same problem with the memory when you use the
pipeline
> > > testing components in the SDK?
> > >
> > > Eric
> > > http://blog.biztalk-info.com
> > >
> > > "Q1andQ2" <Q1andQ2@[EMAIL PROTECTED]
> wrote in message
> > > news:609E04F9-B901-4B71-988E-EA8BFB8885B3@[EMAIL PROTECTED]
> > > > There was a failure executing the receive pipeline: ....Source:
"Flat file
> > > > disassembler" Receive ****t:... URI: ....Reason: Attempted to read
or write
> > > > protected memory. This is often an indication that other memory is
> > > > corrupt.
> > > >
> > > > What the hell is going on?
> > > >
> > > >
> > >
> > >
> > >
|
