Unfortunately there's nothing in the API log to show - it calls +CE on HPD:Help Desk to create the entry - the next item in the API log is after the entry is created. That's a 39 second stretch during which the filter items I mentioned are occurring. The snippet below is directly from the filter log - these lines are consecutive - I just shaved off the beginning parts of the lines in my original post for readability. The two consecutive entries from the arfilter log are verbatim below: <FLTR> <TID: 0000000009> <RPC ID: 0000029441> <Queue: Fast > <Client-RPC: 390620 > <USER: YNZJH0 > /* Tue Apr 01 2008 11:08:00.5076 */ End of filter processing (phase 1) -- Operation - CREATE on SYS:Action - <NULL> <FLTR> <TID: 0000000009> <RPC ID: 0000029441> <Queue: Fast > <Client-RPC: 390620 > <USER: YNZJH0 > /* Tue Apr 01 2008 11:08:03.5168 */ End of filter processing (phase 2) -- Operation - CREATE on SLM:Measurement - 000000000000094
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, April 01, 2008 1:07 PM To: [email protected] Subject: Re: Mysterious gap in log files. ** Post the filter/api log snippets that show the gap with the TID and RPC ID included. Axton On Tue, Apr 1, 2008 at 12:32 PM, William Rentfrow <[EMAIL PROTECTED]> wrote: ** I am trying to tighten up the time it takes to create a new Incident in IM 7.03 (ARS 7.01, Solaris, remote oracle DB). I've checked the threads/queues quite thoroughly and they appears to be fine - there's plenty of available time queue time. However, in the filter log there are multiple places where this happens: Tue Apr 01 2008 11:08:03.6332 */ End of filter processing (phase 1) -- Operation - CREATE on SYS:Action - <NULL> Tue Apr 01 2008 11:08:06.6404 */ End of filter processing (phase 2) -- Operation - CREATE on SLM:Measurement - 000000000000095 Notice the three second gap between those two - there is NOTHING else going on anywhere else in the SQL or API logs to indicate some processing - it's just three seconds of the nothing in all of the logs. Every time there's a "end of filter processing' phase message we just stop for 3 seconds. In my 39-second Incident creation time there are a total of 10 of these gaps - 30 seconds where absolutely nothing appears to be happening. Keep in mind this is a large solaris server and I'm the only one on it - there's no lack of server resources. We've got plenty of hamsters/wheels/etc to power this thing. William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
