Did you turn on clustering? I think tasks only run on the master in a
cluster.
Barry Books
-Original Message-
From: Allan Regenbaum DP [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 8:03 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] URGENT AOLSERVER + ACS + SOLARIS
We
+ ACS + SOLARIS
Did you turn on clustering? I think tasks only run on the master in a
cluster.
Barry Books
-Original Message-
From: Allan Regenbaum DP [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 8:03 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] URGENT AOLSERVER + ACS
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.
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
Is this true of detached threads too - no cleanup? We're probably fine,
but nice to know when to be extra careful.-Jim
Make sure that you explicitly release database handles and ns_sets in
scheduled procs. A connection thread has a bunch of cleanup that it does,
and none of it gets
On Tue, 30 Oct 2001, Jim Wilcoxson wrote:
Is this true of detached threads too - no cleanup? We're probably fine,
but nice to know when to be extra careful.-Jim
I believe so, but it could just be my paranoia.
