Re: [AOLSERVER] aolserver 3.x not running scheduled procs anymore
Thanks everyone - that did the trick! Nice work to the people who tracked that down - quite a thread!! On 10/19/06, Dave Siktberg [EMAIL PROTECTED] wrote: Here is the message from five months ago that helped me get this fixed on my 3.x system: Forum: OpenACS QA Thread: ad_schedule_proc seems to be failing Author: Michael A. Cleverly Posted: 2006-05-23 12:53:52.861061-07 Let me try and explain: During AOLserver startup, if MaxOpen or MaxIdle is a positive number (not zero which means forever) then AOLserver schedules a job to check to reset the database connections at [expr [clock seconds] + $MaxOpen] (as it were). After May 12, 2006, the current time since the beginning of the epoch, plus a MaxIdle/MaxOpen setting of 1 billion seconds resulted in a scheduled event that overflowed a 32-bit signed integer. (It wrapped around and became a negative value.) From what I gather from the AOLserver list, on Solaris this leads to a hard crash in some pthread function call. On Linux it just seems to forever hang up processing of scheduled events (because it can't cope with a negative time and every negative number is less than any positive number). On Linux people who don't have MaxIdle or MaxOpen set at 10 or who haven't restarted AOLserver since May 12th won't have experienced the problem. (For someone with a 1 billion setting who last restarted on May 11th then AOLserver is scheduled to reset the database connections in mid-January 2038 right now...) A setting of 100 million, instead of 1 billion, wouldn't have exposed this condition on AOLserver 3.x for another twenty-eight years or so. Zero is the right value to use now. (Apparently 1 billion was chosen, instead of zero, due to some bug in the Oracle driver or the Oracle client libraries... 1 billion being effectively forever... until this month!) -- 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. -- 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.
Re: [AOLSERVER] aolserver 3.x not running scheduled procs anymore
On 10/18/06, Mark Aufflick [EMAIL PROTECTED] 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? Hi Mark, I think this is the (very interesting) thread: http://thread.gmane.org/gmane.comp.web.aolserver/13037/focus=13058 It came down to the values for MaxOpen and MaxIdle being set improperly. The fix is to set them to zero, if that's the cause of your specific problem. Vinod -- Vinod Kurup, MD [EMAIL PROTECTED] http://kurup.org -- 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.
Re: [AOLSERVER] aolserver 3.x not running scheduled procs anymore
On 10/18/06, Mark Aufflick [EMAIL PROTECTED] 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? All the gory details and more at: http://dossy.org/archives/000319.html Michael -- 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.
Re: [AOLSERVER] aolserver 3.x not running scheduled procs anymore
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.
Re: [AOLSERVER] aolserver 3.x not running scheduled procs anymore
Here is the message from five months ago that helped me get this fixed on my 3.x system: Forum: OpenACS QA Thread: ad_schedule_proc seems to be failing Author: Michael A. Cleverly Posted: 2006-05-23 12:53:52.861061-07 Let me try and explain: During AOLserver startup, if MaxOpen or MaxIdle is a positive number (not zero which means forever) then AOLserver schedules a job to check to reset the database connections at [expr [clock seconds] + $MaxOpen] (as it were). After May 12, 2006, the current time since the beginning of the epoch, plus a MaxIdle/MaxOpen setting of 1 billion seconds resulted in a scheduled event that overflowed a 32-bit signed integer. (It wrapped around and became a negative value.) From what I gather from the AOLserver list, on Solaris this leads to a hard crash in some pthread function call. On Linux it just seems to forever hang up processing of scheduled events (because it can't cope with a negative time and every negative number is less than any positive number). On Linux people who don't have MaxIdle or MaxOpen set at 10 or who haven't restarted AOLserver since May 12th won't have experienced the problem. (For someone with a 1 billion setting who last restarted on May 11th then AOLserver is scheduled to reset the database connections in mid-January 2038 right now...) A setting of 100 million, instead of 1 billion, wouldn't have exposed this condition on AOLserver 3.x for another twenty-eight years or so. Zero is the right value to use now. (Apparently 1 billion was chosen, instead of zero, due to some bug in the Oracle driver or the Oracle client libraries... 1 billion being effectively forever... until this month!) -- 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.
