Are you exec'ing anything in the scheduled proc? I've seen some weirdness in the past with execs getting hung, although not much recently. I think it was more of an OS (Linux) issue.
We've used scheduled procs for years w/o any problems on all of our servers, though we only have a handful (of scheduled procs), like 10. whereas I've read that ACS has lots of them. A suggestion would be to run more complex stuff in detached threads that you launch from the scheduled proc rather than in the scheduled proc itself. Then if it screws up, you won't tie up the scheduler thread. Jim > > I have *always* had a problem with scheduled procs, to the point where I now > simply use a cron job and curl to tell AOLserver to do something.... > > Michael > > Allan Regenbaum DP wrote: > > > We are running a production AOLServer 3.3.1 + ad13 on solaris > > We have 2 machines, duplicates of each other. > > > > Machine A suddenly, without error messages stops running scheduled procs !! > > Machine B continues to perform flawlessly > > The machine is running acs classic 4.2 tcl, 90% webmail which has been > > running perfectly well under stress and load for months... > > > > Urgent help/suggestions are appreciated .. > > > > Allan Regenbaum > > Digital People >
