Hi Scott,
Thanks for your reply.
I don't think that I can send the log as it will be so big , as AOlserver
initiates and load a lot of ACS code...
And for the checksum, we did the following:
Using pound, we shifted the load going to this webserver to another server
on another machine where it
It appears that you have the same problem in all of your servers; the
goal is to find out what part of the code is failing and under what
conditions. Three things stand out: failed servers are under a heavier
load than those that don't exhibit the failure; the failure happens
shortly after
Hello,
From my experience, I think the problem may be related with the 64 bits.
I've servers with AOLServer 32 bits, and AOLServer 64 bits, and I have
seen 64 bits growing faster in memory (and even not decreasing through
time), until it takes a considerable amount of memory (then I have to
Hi Juan,
That's a good point. I noticed Rami was hosting on 64 bit AMD systems
and it is possible that if he were running on a 32 bit architecture
the problems he's experiencing might not surface. This could mean a
problem with Tcl on 64 bit or something specific to AOLserver. I
suspect
Rami,
it looks to me as if the problem is due to a c-extension you are using
and happens after a thread exit. When a thread exists, it frees among
other things the associated tcl interpreter. At this time, all c
extensions have to unload cleanly as well. Note that ns_eval creates
and destroys as
