- This topic has 2 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
I am using BizTalk server 2004 on Windows 2003 server. Recently we found that the server was leaking memory. We took a counter of the available bytes on the server and we found it to degrade from 3 Ghz to 1 Ghz. When we did a clean up of the messagebox database and the biztalk tracking database and then did a reboot of the server, we realized the we were regaining the lost memory.
We thought it to be a problem with the OS patches and installed the latest version of the Windows 2003 service pack1 and then even installed Microsoft Biztalk server 2004 service pack1. Even then the memory leakage continued. We are quite unsure on how to proceed with this problem.
We started to notice this on a business day when we realized that messages flowing into biztalk were not coming out. We realized the biztalk server was not responding. As a temporary solution we restarted the BizTalk server application and then restarted all dependent services on other servers. It did bring back the application to start. On investigation we found a number of FILE adapter failure instances on the event viewer logs. This situation repeated itself for many times and during all those times we noticed the FILE adpater failing and we had to restart the services. It was only on further investigation we realized that the BizTalk server was leaking memory. But interestingly we then came to know the BizTalk server reboot only caused the entire chunk of memory to be regained.
We are still unsure of where things are going wrong for us.
Any suggestions or directions are most welcome.
Thanks.
Duraivel
-
Hi Greg,
Thanks for the timely response. First of all, the following conditions were the ones that led me to conclude that the memory leak could be causing the BizTalk server from responding.
1. Performance graphs have indicated that the memory leak occurs once the BizTalk server has been restarted and continues till the next time it is restarted.
2. There are other Windows 2003 servers in the same environment and the memory graphs for them do not show any kind of leakage. If what your saying about the memory leakage is acceptable, then that trend should have been observed on all the other servers too. But that is not the case.
3. We do a BizTalk clean up of the databases and then reboot the server. On days when the server gets rebooted, the BizTalk server seems to have responded exceptionally well. And then when the same job is run for the next day we have experienced delays. We keep observing these delays till the day when BizTalk server is restarted again. On that day again the job response time was noted to be exceptionally well. Thats why we started attributing the memory issue to the responsiveness of the BizTalk application.Also, with regards to the FILE adapter failures, I see the following message as a warning event in the event viewer logs of the BizTalk server.
\”The adapter failed to send the message to the send port \”D:\\AIApplicationHome\\BTSApplicationHome\\NICE\\temp\\requestinstance\\%MessageID%.xml\”. It will be resent after the retry interval specified for this send port.\” Event Id: 5786
The folder location is the place where we send the xml files to get stored. We initially thought that it could be a problem only with a particular xml file. So we tracked down the job and reran it again only to find that at the other instance the job ran fine without any FILE adpater warnings. We also observed that during the retry interval for this adapter failure, the FILE adapter just does not do any other processing even though there are other orchestrations which require it.
We arrived at the conclusion that the memory leakage was causing the FILE adapter failure which in turn led to the bad response ( or no-response) state of the system. We even found out a microsoft article which spoke of a memory leakage in the FILE adapter. The article can be seen at http://support.microsoft.com/?scid=kb;en-us;886226&spid=1444&sid=297
The article suggests that we use the latest service packs on the server. We did try that out and still found out that the issue was recurring.
Please let us know in case if we are missing anything or if our understanding is wrong.
Our sincere thanks for all the efforts.
-
A memory leak is where a process acquires memory and then forgets about it and keeps acquiring more. This only becomes a problem when there is no more memory.
Most server based processes will acquire memory and keep it for reuse, this saves the overhead of re-acquiring the memory later. So over time a process’ memory use will increase. Hopefully to a steady state. If you have lots of available memory all the time, then you have paid for something you didn’t need.While you may have a memory leak, I do not believe this is causing Biztalk processing to fail. You still have 1 GB of RAM available so Biztalk is not constrained by a memory shortage.
You say that the FILE adapters are failing. This is more likely to be the cause of the problem rather than a symptom. What is the error message in the event log
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.