Right now we are on Patch 003. I will look at the documentation for Patch 6 or 7. I am wondering if the report thing is just a symptom but it may be the whole problem. The timing is just off on when everything started to happen and how it is progressively getting worse. Thank you for the info. I will check it out now.
From: "Grooms, Frederick W" <[email protected]> To: [email protected] Date: 11/24/2009 06:09 PM Subject: Re: Process Hanging Sent by: "Action Request System discussion list(ARSList)" <[email protected]> ** Which ARS 7.1.0 patch level are you on (Patch 8 was released on November 20th)? I think Patch 6 or 7 fixed a bug relating to reports. Fred From: Action Request System discussion list(ARSList) [ mailto:[email protected]] On Behalf Of Brandi Barbour Sent: Tuesday, November 24, 2009 5:02 PM To: [email protected] Subject: Process Hanging ** All, We have our production server that has been hanging for about a month now. I have been working with support to figure it out but as of yet we have not found the underlining issue. So I am hoping someone else has seen this problem. ARS 7.1.0 ITSM 7.0.3 SQL 2005 on remote server Windows 2003 We turned on and configured SLM and about or right at that time our system became slower and it started hanging up. The arerror.log only shows the following: Tue Nov 24 16:25:15 2009 390635 : AR System server terminated when a signal/exception was received by the server (ARNOTE 20) Tue Nov 24 16:25:15 2009 0xc00000fd Tue Nov 24 16:25:15 2009 390635 : AR System server terminated -- fatal error encountered (ARNOTE 21) in the arthread log it shows: <THRD> /* Tue Nov 24 2009 10:52:12.5620 */ Thread Trace Log -- ON (AR Server 7.1.00 Patch 002 200802011900) <THRD> /* Tue Nov 24 2009 14:04:27.7550 */ Thread Id 1936 (thread number 24) on LIST queue died. <THRD> /* Tue Nov 24 2009 14:04:27.7550 */ Thread Id 1904 (thread number 24) on LIST queue restarted. <THRD> /* Tue Nov 24 2009 14:05:19.9140 */ Thread Id 3420 (thread number 38) on FAST queue started. Always a LIST queue that dies; We have increased threads: Private-RPC-Socket: 390601 1 1 Private-RPC-Socket: 390603 2 2 Private-RPC-Socket: 390620 12 20 Private-RPC-Socket: 390626 2 3 Private-RPC-Socket: 390635 12 20 Since we have 4 processors (well really 2 with 2 core) The Filter-Max-Total was changed since we have the ITSM suite. Filter-Max-Total: 500000 Filter-Max-Stack: 10000 I have changed any Custom escalations that may have some sort of hit on the system to either in off hours or to at least less frequent. Now the problem seems to be anytime we have someone run a report or what most likely is happening is 2 people are running reports the system hangs. The user tool hangs up and the process for arserver.exe has a memory usage of either over 800,000K or just under that. The actual service does not stop however you can not do anything until the service is restarted. As this is a fairly new system it now has more users then ever and more actions are being taken. However with it crashing around 6 times a day it is not useful. Turning on SLM may be just a coincedence however we have a lot of Service Targets. Has anyone seen this and the memory usage going that high? Support wants me to limit the search to 1000. But we have way more that many tickets in one day and Management will not allow that to happen. Any help would be appreciated. Brandi _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
