Thread logging will only show thread initialization/termination info. To see what the threads are doing via arserver, you have to collect the api logs.
You didn't state which platform you are using, but f you want to see at a lower level what the various threads are doing on Solaris, you can use pstack, which prints a stack trace for each lwp for each process. Another approach would be to observe the queue statistics using the Server Statistics. This will probably help you narrow down, to the queue, where to look, if in fact the issue is related to some type of thread locking issue. Axton On 10/22/07, Shawn Stonequist <[EMAIL PROTECTED]> wrote: > Greetings List!! > > I'm wondering if there is anyway that can be used to view specific thread > IDs. > > I ask because it seems every Monday, between 8am & 10am, our ARServer slows > significantly. We've held off doing various "Monday Morning" reports & > backups, but without any improvement. > > Our DB believes that the issue is being caused by a thread, but can't tell > which one. > > I ran our "Thread Logging" in the System Config, but I only got ID's and > when they started (2, but only just after we received the complaint about > the Server's performance). Unfortunately, this log doesn't say *what* these > threads were doing. > > It is my hope that, by finding out what these threads are doing (even if I > have to start the Thread Logging on the previous Friday, weekends are > low-to-no activity anyway) we can determine what is causing this issue- > errant search? user with a bad query? automated system? etc. > > Huge thanks in advance to all!!! > > Shawn Stonequist > Remedy 6.3 > EMNS > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
