Marcelo, It sounds like your server is maxing out in memory...would need to do some additional testing of course to verify....but when saving there are two different types of memory management. One is 'Development Cache Mode', the other is commonly called 'Production Mode'....here is basically how it works. Dev Cache mode takes the current object cache in memory and locks it, makes changes to it, then makes it available again....this means while changes are made to the code the server becomes unavailable to users, but the server only has one copy of the cache in memory at any time. The 'production' mode attempts to keep the server available while making the changes...so the server makes a copy of the cache, makes changes to the copy, waits for all processes to stop using the original copy, then drops it. This process keeps the cache available to users, but causes significantly more memory in large installations. If your server is a Dev/Test server, I suggest turning on dev cache and restarting the server. If this is Prod, I first off don't recommend making changes directly there....but if this is during a 'release', the way we deal with that is to move it into dev cache mode, restart it, make our changes, take it out of dev cache mode, restart it....
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Martinez, Marcelo A Sent: Tuesday, March 30, 2010 8:08 AM To: arslist@ARSLIST.ORG Subject: arserver.exe performance saving workflow I'm having an issue trying to save workflow via the admin tool. I'm just doing basic enable/disable function of workflow. The issue is that after I disable a workflow and press save, the memory usage of arserver.exe jumps from less than 600mb to over 1gig. The problem is that the change to the workflow never happens, it times out; and then, after the time out, the memory does not go back down below 600mb. None of my users are seeing any performance issues, just me through the admin tool. I checked under the application event log (windows) and noticed I have a many "informational" entries for AR System Monitor which read: 390620: AR System server terminated when a signal/exception was received by the server (ARNOTE 20). And also: 390620: AR System server terminated - fatal error encountered (ARNOTE 21). I also see many VsJITDebugger error entries. I proceeded to reboot the server last night and tried saving my workflow again, same thing happened. My arserver.exe runs at below 600MB, then when I attempt to save it, it jumps up to 1.2gb. then the memory does not seem to get released and I cannot save any workflow. As of today, I have not seen any AR System Monitor entries in the application log, but I am afraid to attempt to work on any workflow. Has anyone experienced similar issues? Or can advise on how to troubleshoot. Environment: Win 2003 SQL2005 ARS 7.1P7 Thanks, Marcelo ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
