The memory consumption may be caused by a long-running stored procedure or orchestration. If the BizTalk Server process uses about 1 GB of RAM, there might be a memory leak or a high memory situation. For example, if the BizTalk Server has 4 gigabytes (GB) of RAM, and the BizTalk Server process uses about 500 megabytes (MB) of RAM, there may not be leak. For this issue, consider the following: Physical RAM and memory usageīecause it may be expected behavior for a process to use about half the physical RAM, use the memory usage as a guideline. A memory leak may cause an out-of-memory exception when memory usage increases until the process runs out of system memory or until the process stops functioning. The BizTalk Server process may be experiencing a memory leak when memory usage in Microsoft Windows Task Manager consumes more than 50 percent of the physical RAM. These considerations include the following things:
This article discusses important things to consider when you evaluate memory usage and possible memory-related issues.
You may have to try several steps to find the specific cause of a memory leak or an out-of-memory (OOM) exception in Microsoft BizTalk Server. Original product version: BizTalk Server 2010, 2009 Original KB number: 918643 Summary
#User defined memory monitor server 2012 how to#
This article describes how to troubleshoot a memory leak or an out-of-memory exception in the BizTalk Server process of Microsoft BizTalk Server.
0 kommentar(er)
