Forum Discussion
BizTalk process Host is not releasing memory until Hosts are manually restarted
The BizTalk process Host is not releasing memory until Hosts are manually restarted (Ideally it should release the memory that is not in use) We tried terminating all running/suspended instances, ...
Hi Akash_Chubb Have you been able to resolve the problem? We are experiencing exact same symptoms and frankly have no idea how to approach the situatiion.
sanoraya Hi
Yes
I found issue in our logging component, It was causing memory leak, I wrote a custom logging component & replaced and used it everywhere.
NiklasEMicrosoft
I have seen a few issues with logging frameworks leaking memory objects, e g config file watchers and timer objects. Since it was related to timers and events being fired, it was also using more and more resources. I could see millions of .NET objects in memory dumps. So it can be good to replace older logging frameworks and have more control over this yourself if you need logging. As a workaround until you replaced the logging, if not leaking too much memory you could e g on daily basis restart the BizTalk host or set recycling period of the IIS application pool if this is in isolated host.Thank you Akash_Chubb for the update. I am dealing with the same issue, got to find the leaking component