I figured you had especially after you noted the arf and arv files hadn't changed.
Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Thu Sep 27 06:58:49 2007 Subject: Re: Delays after user tool sits idle ** Yup. I'm an "old-timer" too; and have cleaned the cache. This is happening across the board, and is not limited to specific PC's or users. -- Tony Worthington Sr. Technical Analyst Kohl's Department Stores [EMAIL PROTECTED] 262-703-5911 "Shellman, David" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/26/2007 03:59 PM Please respond to [email protected] To [email protected] cc Subject Re: Delays after user tool sits idle ** Have you dearfed? One trick that many of us old timers do is delete all the directories associated with arf and arv files. These have known to become corrupted and will cause apparent slowness. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tony Worthington Sent: Wednesday, September 26, 2007 4:51 PM To: [email protected] Subject: Re: Delays after user tool sits idle ** Yup. The white screen of nothing. That's it. -- Tony Worthington Sr. Technical Analyst Kohl's Department Stores [EMAIL PROTECTED] 262-703-5911 "Kendhammer, Mike" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/26/2007 03:21 PM Please respond to [email protected] To [email protected] cc Subject Re: Delays after user tool sits idle ** Hey Tony, My support desk just informed me today of similar issues. One analyst reported that she went to click on the Remedy User Tool to maximize from the Taskbar and it took two minutes to max, then took another number of minutes to open a new ticket from the control panel. All these times there is a blank white screen with the Remedy border showing. It doesn’t happen all the time though and I am just beginning troubleshooting the issue. We are on 7.0.1 p 2 Interesting… Mike ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tony Worthington Sent: Wednesday, September 26, 2007 1:43 PM To: [email protected] Subject: Re: Delays after user tool sits idle ** Nope.. as mentioned in one of my previous posts... :-) >We have no remote clients here, everything is on the local network with no >firewalls or proxies between the clients and the server (only one edge >switch.) -tony -- Tony Worthington Sr. Technical Analyst Kohl's Department Stores [EMAIL PROTECTED] 262-703-5911 "L. J. Head" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/26/2007 01:40 PM Please respond to [email protected] To [email protected] cc Subject Re: Delays after user tool sits idle ** Is there a firewall between the client and Server?...as mentioned by another poster ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tony Worthington Sent: Wednesday, September 26, 2007 12:02 PM To: [email protected] Subject: Re: Delays after user tool sits idle ** That's where I'm stuck. All the workflow and server logging fails to capture that initial "lag." An example.. I had a query results list and record selected in my user tool, and left it there for approx 20 minutes. I then selected another record in the list. What should have taken less than two seconds (display the new record) took over 30 seconds. The logs don't reflect that lag, and in fact don't start logging that (or any) action until the tool "unfreezes." <API > <TID: 0000000292> <RPC ID: 0000284431> <Queue: Fast > <Client-RPC: 390620 > <USER: Demo > /* Wed Sep 26 2007 12:59:09.5130 */+GLS ARGetListSchema -- changed since Wed Dec 31 18:00:00 1969 from Remedy User (protocol 12) at IP address 10.2.120.14 <snip> <API > <TID: 0000001984> <RPC ID: 0000284445> <Queue: List > <Client-RPC: 390620 > <USER: Demo > /* Wed Sep 26 2007 12:59:11.0720 */-GLEWF OK The exact same action when the user tool has not been idle, performs as expected. -- Tony Worthington Sr. Technical Analyst Kohl's Department Stores [EMAIL PROTECTED] 262-703-5911 Carey Matthew Black <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/26/2007 11:47 AM Please respond to [email protected] To [email protected] cc Subject Re: Delays after user tool sits idle Tony, I would look at the client active links logs (and if you can Server side API/SQL logs) to see if your actually facing a DB issue. Maybe there is some workflow doing a search that is not as well indexed as it should be and the DB is swapping the table out of active memory and needing to shuffle things around or do a table scan? Such problems have a way of "just happening" due to data growth or an increase in volume of user activities over time. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/26/07, Tony Worthington <[EMAIL PROTECTED]> wrote: > ** > All - > > Has anyone experienced the issue of the User Tool taking an extremely long > time to perform any action after sitting idle for a few minutes? Click, > wait a minute, then poof everything is back to normal. > > We have 7.0.1p3 delpoyed, and I also see the same issue using the 7.1 tool. > I'm going to open a ticket with support, but I was hoping for some "me > too's" or tips. :-) > > (Nothing in client-side logging other than a gap where the tool is frozen.) > > Thanks, > Tony > > ITSM7.0.2p4/win2kr3/10gr2 > > > -- > Tony Worthington > Sr. Technical Analyst > Kohl's Department Stores > [EMAIL PROTECTED] > 262-703-5911 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
