On Fri, Jun 16, 2006 at 10:22:46AM +0100, Brian Fenton wrote:
this is useful information. I do occasionally see these messages in the
error log: Warning: sched: excessive time taken by proc 8 (43
seconds), so I guess that's the behaviour you describe. And it explains
So what are my options
This raises the question for me, should all scheduled procs be run in
their own thread to avoid creating these kinds of problems where other
procs get affected?
This really depends on how crucial it is that the proc actually run every
(say) 15 minutes. Something that sweeps a queue of
@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Scheduled proc occasionally not running
On Fri, Jun 16, 2006 at 10:22:46AM +0100, Brian Fenton wrote:
this is useful information. I do occasionally see these messages in
the
error log: Warning: sched: excessive time taken by proc 8 (43
seconds), so I
.
Brian
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf
Of Andrew Piskorski
Sent: 16 June 2006 14:43
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Scheduled proc occasionally not running
On Fri, Jun 16, 2006 at 10:22:46AM +0100, Brian Fenton
?
Thanks
Brian
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf
Of Tom Jackson
Sent: 14 June 2006 17:07
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Scheduled proc occasionally not running
My guess is that possibly another scheduled proc
Hi AOLserver gurus!
I have a problem where a proc scheduled with ns_schedule_proc to run
every 300 seconds occasionally doesn't run.
I have 2 production systems where this occurs - one is AOLserver 4.0.10,
the other AOLserver 3.3+ad13. The software is identical on both systems.
It appears to
My guess is that possibly another scheduled proc is running for too long a
time, and not running in a thread. When the scheduled time for your proc
arrives, the scheduler is busy running another proc. This usually shows up in
the error log with a statement that the scheduled proc took too long
