The problem was that the very large value we all use for MaxOpen and
MaxIdle on the database pools causes an integer overflow (I think) in
the time calculation. You need to set them to a smaller value, or
set them to zero; that is supposed to have the same effect (keep
them open indefinitely) and it seems to be working ok on the one site
I had to do this on.
janine
On Oct 18, 2006, at 7:38 PM, Mark Aufflick wrote:
I remember some time ago (maybe last year) people complaining that
their aolserver 3.x servers stopped running scheduled procs. My sole
remaining 3.x site didn't exhibit the problem and I didn't pay too
much attention.
A few weeks ago, however, my (still sole remaining) aolserver 3 site
stopped running scheduled procs!
Can anyone remember if anyone found the root cause of this?
Mark.
--
Mark Aufflick
e: [EMAIL PROTECTED]
w: mark.aufflick.com
p: +61 438 700 647
f: +61 2 9436 4737
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
