Chances are the admin thread is busy doing other things.  Group name
changes, group creation, etc. will all tie up the admin thread for a
period of time that is in direct correlation to the number of users
and groups in the system for those operations.  If you turn on api
logging, you can grep the logs for everything that is running on queue
390600 (admin queue) to see what the thread is busy doing.  It could
be any number of things though, run process commands triggered by an
operation performed on the admin queue, etc.

Axton Grams

On 5/26/07, Janie Sprenger <[EMAIL PROTECTED]> wrote:
**



Hi,



Wondering if anyone has seen this or has some ideas to resolve:



ARS 7.0 patch 2

ITSM7 apps installed

Win2003 Server

SQL DB



The problem is:  Admin tool has started locking up after about 2 minutes of
idle time, then click on any object and it hourglasses.  Error returns –
failed to load forms from server.  While the admin tool is locked the user
tool functions perfectly fine.  This happens for all admin accounts on
multiple machines (which would make sense with one thread)—also happens when
only one admin is logged in.  We have to restart the AR Server service to
recover.  Fortunately, it's a dev environment.



So, here are things we have done to try to figure out the issue:   If we
start the service manually from a command line  arserver –m  the admin tool
does not lock up.   When starting from services – admin tool locks.  In the
armonitor.cfg file we have reduced the processes starting to only arserver –
still locks up.  We have tried patching the admin tool – still locks.  We
also tried reinstalling arserver with the 'Administrator' user account on
that box—still locks.  We've added debug-mode to ar.cfg and aren't seeing
anything out of sorts in the logs.  We've tried starting the service as the
local admin – still locks.



We're concluding that maybe there is a connectivity issue, although—we're
not certain as to how that could be, since the user tool works fine.



So, I'm wondering if anyone has any ideas as to what they think the problem
could be, or places to look to troubleshoot/resolve.



Thanks in advance.





Janie

  __20060125_______________________This posting was
submitted with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to