Wednesday, February 23, 2005
BizTalk Server 2004 PowerToys
Thanks to Erik we've got an overview of very usefull and excellent downloadable BizTalk utilities. Go and have a view here.
Comments:
<< Home
Hello Danny,
I am at a loss and in need of some guidance/assistance. I have been architecting a company conevrsion / EAI process using BTS04. It was going smooth until we started mapping large files. We found that everytime we mapped a file larger then 100,000 rows or 10mb, it would throw an OutOfMemory exception and suspend the message. I have been been back & forth with MS about this issue, and concluded that it is a limitation in BTS04. (Well, actually in the .NET1.1 framework DOM mapper) Also, concluded that there isn't any talks about correcting this issue in the near future.
Now, I stumbled upon your post on that stated:
We are indeed processing messages from about 100MB and had the same problem
with mapping.
We created our own mapping logic in an .NET component, like this we where
able to work around the problem.
My question to you is how did you write this custom mapper logic? Does it still function okay? What is the max file size limit? Do you have any samples that you can possibly provide?
I have been ripping my hair out trying to find a workaround. It has been over 2months worth of architecting & testing, and I really would hate to conclude it a waist of time.
thank you in advance,
Jason
jworkman1[at]comcast.net
Post a Comment
I am at a loss and in need of some guidance/assistance. I have been architecting a company conevrsion / EAI process using BTS04. It was going smooth until we started mapping large files. We found that everytime we mapped a file larger then 100,000 rows or 10mb, it would throw an OutOfMemory exception and suspend the message. I have been been back & forth with MS about this issue, and concluded that it is a limitation in BTS04. (Well, actually in the .NET1.1 framework DOM mapper) Also, concluded that there isn't any talks about correcting this issue in the near future.
Now, I stumbled upon your post on that stated:
We are indeed processing messages from about 100MB and had the same problem
with mapping.
We created our own mapping logic in an .NET component, like this we where
able to work around the problem.
My question to you is how did you write this custom mapper logic? Does it still function okay? What is the max file size limit? Do you have any samples that you can possibly provide?
I have been ripping my hair out trying to find a workaround. It has been over 2months worth of architecting & testing, and I really would hate to conclude it a waist of time.
thank you in advance,
Jason
jworkman1[at]comcast.net
<< Home
