Aug 03 2020 09:00 PM
The BizTalk process Host is not releasing memory until Hosts are manually restarted (Ideally it should release the memory that is not in use)
The memory slowly piles up and each of the service calls (WCF Web Service calls) starts getting delayed, taking around 10 mins to proceed (even when we clearly see on WCF Web Service Servers that response from service was sent on time within a minute)
Everything goes back to normal and speeds up as soon as we manually restart process host instance
Aug 03 2020 10:01 PM
We have migrated Code from BizTalk Server 2010 to 2016 hosted on cloud and facing weird behavior.
On processing message of 16 MB of flat file simultaneously(2MB each), the memory consumption on task bar is around 2.5 GB.
Regarding Orchestration:
I don’t think the issue with the orchestration as the code was running good on BT2010.
Problem:
Memory Reading on Task Manager against the host instance after terminating the all messages is not changing. where as Perfmon showing flat zero when there were no messages processing.
Also after couple of mins when we tried to process a small file.. Reading came down to 1 or 3 MB. But again it went to constant reading.
Initially we thought it could be memory lead, but doesn’t appear to be. There is no unmanaged code, but lot of file write operation using RollingFlatFileTraceListenerData Class
Additionally – Few observations:
Discrepancy: Task bar showing 2.5 GB where as Perfmon showing flat zero when there were no messages processing.
High Utilization: Under huge load 16 MB Flat File (2 MB file each) memory utilization was 2.5 GB , after terminating messages memory utilization stuck- up at 2.5 GB.
May 21 2021 12:09 AM
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.
May 24 2021 02:13 AM
@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.
May 24 2021 08:53 PM - edited May 24 2021 08:53 PM
Thank you @Akash_Chubb for the update. I am dealing with the same issue, got to find the leaking component
Sep 15 2021 02:00 PM