The incomparable Mikael H%u00e5kansson has just published the details of my next visit to Sweden this September. After I told Mikael about my latest book, we thought it might be epic to put together a 2 day workshop that highlights the “when to use what” discussion. Two of my co-authors, Stephen Thomas and Ewan Fairweather, […]
I have seen many BizTalk customers running into OutofMemory Exception while calling a map from inside the Orchestration, so I thought this blog post should help.
Typically, this happens when we are calling a map from inside the Orchestration and the map is inside a large assembly. This was a known issue and was documented at http://support.microsoft.com/kb/918643
“The System.Policy.Security.Evidence object is often used in transforms and can consume much memory. Whenever a map contains a scripting functoid that uses inline C# (or any other inline language), the assembly is created in memory. The System.Policy.Security.Evidence object uses the object of the actual calling assembly. This situation creates a rooted object that is not deleted until the BizTalk service is restarted.
Most of the default BizTalk functoids are implemented as inline script. These items can cause System.Byte[] objects to collect in memory. To minimize memory consumption, we recommend that you put any map that uses these functoids into a small assembly. Then, reference that assembly.”
So for example if you have got the map inside a 10 MB Assembly, it will always create 10 MB System.Byte[] objects in the memory and you can imagine how quickly you could run into the OOM Exception if you are on a 32 bit environment. Earlier only workaround was to put map in the small assembly but if you are not able to split the maps and other artifacts by different project, then the good news is that this issue is fixed in http://support.microsoft.com/?id=975118.
This hotfix has been released for BizTalk 2006, BizTalk 2006 R2 and BizTalk 2009. Also, this hotfix is part of BizTalk 2006 R2 SP1.
I have seen that this hotfix improves memory utilization by the orchestration hosts. This also helps increase performance and stability of the BizTalk applications. If you haven’t got this fix as of yet, I will highly recommend to apply this fix ASAP.
For those of you that attended the “Real World SOA with .NET and Windows Azure” TechEd session that John deVadoss, Christoph Schittko and I did last week, I discussed the following reference architecture:
I didn’t have time to do a demo/walkthrough during the session, but as I mentioned, recordings are available:
Thanks all that attended, we had fun, and the feedback has been great.
This is the third in a series of posts on the new features included in BizTalk Server 2010 Beta. Enabling the BizTalk mapper and the BizTalk Adapter Pack in Windows Workflow Foundation is the starting point of Microsoft’s aim for a deep integration between BizTalk Server and Windows Server AppFabric. The first added feature is […]
I opened up a codeplex project for housing some custom WCF binding work I have been doing: http://customwcfbindings.codeplex.com/.I uploaded my progress on a custom SalesForce binding based on the WCF LOB SDK if you want to take a look. There are a couple bugs I would like to get out of the way before making […]
You can now download the beta of BizTalk 2010 from the BizTalk site at Microsoft: www.microsoft.com/biztalk
Please have a look, I’ve been running it for a while now and it looks good thus far.
If you encounter any issues please contact me: [email protected]
At Pluralsight, we just released all of our .NET training videos for the iPad. If you’re a subscriber, you can get them now.
Last week at TechEd in New Orleans, we gave away 1000 complimentary subscriptions to the Pluralsight On-Demand! training library. It’s a white plastic card that looks something like this:
If you activate this card by 6/18 (next Friday), you will receive a 2-week subscription to our training library and you’ll be automatically entered to win a brand new 64 GB iPad sitting here on my desk (unopened). The winner will also receive a 1-year Professional subscription to Pluralsight On-Demand!, which makes it possible to fill up your the iPad with our .NET training courses.
We will announce the winner on 6/21. Will we announce it on Twitter (follow @pluralsight) and email the winner.
Don’t forget to activate your card – it only takes a few seconds. Instructions are on the back.
Just came across this great sitewith a collection of color schemes for Visual Studio 2010 and older versions too. There are some real beauties there. I quite like the retro look of Turbo-Pascal Revisited (though i doubt i could use it for a long time without drowning in the blue) and have started to use […]
TechEd North America 2010 is a wrap. You can grab the demos from both of my sessions here. Hope you enjoyed them.
Feel free to connect with me on Twitter (@skonnard) to stay in touch after the event. Also, I’ll be posting a bunch of pictures from the week to the Pluralsight .NET Training page on Facebook.
One of my favorite experiences from the week: we ran into a street band while walking back to the hotel one night, they were jamming New Orleans style and everyone was watching this little girl dance away. Awesome.
It’s been far to long since I’ve talked here about what I’m working on, so it is time to correct that. I’ve been working with a client who has some very unique business requirements, and one of them deals with a lot of flexibility of their data storage. As such we were looking into different types of storage, because while SQL Server is in fact a wonderful product, it is not known for its flexibility of storage.
This quest led us to the door of a large number of databases in the “No SQL” arena, and eventually to MongoDB. MongoDB is a document database, which stores what can best be described to the .NET Developer as a Dictionary<string,object>. This structure allows for nesting of structures (where the object stored is another Dictionary) and is a very clever structure if you ask me. But, document databases do not work like relational databases. There are several important things you need to realize:
In the world of .NET there are several drivers, but the one my team, David O’Hara and Craig Neuwirt and I, decided on was MongoDB-CSharp. They have just released version 0.9 beta 1, which moves the driver a lot closer to a familiarity level for most .NET developers. Now we had to address on our project all of the above problems, and key to us doing so has been a component called DictionaryAdapater from the Castle Project. But that is a topic for another blog post.