Paul, RE: 2. Does anyone have any idea of a way to detect these before it gets real bad, other than looking for steady thread growth?
If time that it takes to get "3rd party vendor information for the site a device is associated with" is impacted for "other" sites (not the site on which all threads are stuck) it may be enough to run a fairly simple health check transaction (better through Remedy and not direct SQL) once every few minutes. Transaction time outside defined boundaries may be used to raise an alarm to let you know that things are bad. It would avoid having to run a query against every site or depend on a thread count. It may also be useful to try to recreate an outage in a controlled environment that is causing the problem that you are describing (to avoid having to wait for an issue to show itself on a live system). This could also be a fairly simple set of transactions (read + insert all for a single vendor) but run with a larger simulated user population. Probably few options on how this can be done but let me know if you need any help. Regards, Armen Avedisijan Scapa Technologies Limited _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"

