When you write a custom pipeline component, loading entire message into memory should be avoided. If you use Memory Stream for large files, it loads entire message into memory and you may have OutOfMemory exceptions. On the other hand, VirtualStream uses Biztalk’s buffering directory after a threshold value which is specified in object initialization. In [...]

Whenever a map contains a scripting functoid that uses inline language like c#, BizTalk Map assembly is created in memory. The object in memory is not deleted until the Biztalk service is restarted. This means every mapping operation causes the whole assembly to be loaded into memory. That’s why we must keep maps and schemas in a [...]

My problem is BizTalk Ftp Adapter’s inability to run in 64-bit mode… Actually, this is one of the problems of the ftp adapter but I won’t write about it in this entry, I can live with it…. Out-of-the box Ftp Adapter receive location deletes files from the remote ftp site so it requires write permission [...]

I want to share some of my notes about Biztalk Server 2006 performance in terms of programming and configuration. This is just a startup and I will try to share my future findings about Biztalk performance in this entry. I also put some related links at the end of the entry for detailed information. Change [...]

While you publish your Schema or Orchestration as a Webservis, You may have routing exception which is one of the many other exceptions most probably you will have A message received by adapter “SOAP” on receive location “WebService_WSUpload/WSUpload” with URI “/WSUpload/WSUpload.asmx” is suspended. Some problems that can cause this problem: The destination orchestration or send [...]