Dear all,

I've got a question (possibly a newbie's one) on the memory
allocated by Aolserver (4.0.10) when running OpenACS (5.1.5).

When monitoring (with "top" or "atop") the memory used by Aolserver running
an OpenACS based Web application it is possible to notice that the value of
virtual memory allocated by the "nsd" process always grows and never ever
gets smaller.



I suspected this continuous growth of the allocated virtual memory was due
either to tDOM or the Aolserver memory allocator. I made sure in my
application that every time tDOM is used its allocated memory gets
explicitly released, but still no luck. So I guess the problem could reside
in the Aolserver memory allocator.



Any clue, any suggestion?  Am I doing something wrong?



I'd like not to be forced to schedule a nightly restart of the server just
to keep the memory allocation problem under control.



Thanks in advance for your help,

Maurizio



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <listserv@listser
v.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
 field of your email blank.

[ Post a follow-up to this message ]

We had a site that was doing this, and the fix in this post worked  
for us:

http://dossy.org/archives/000108.html

It was rather perplexing;  only one of our many hosted sites had the  
problem, and it just started exhibiting it one day with no obvious  
change to account for it.  Based on Dossy's description that  
shouldn't be possible.

janine

On Mar 9, 2007, at 1:38 AM, Maurizio Martignano wrote:

> Dear all,
>
>                 I’ve got a question (possibly a newbie’s one) on  
> the memory allocated by Aolserver (4.0.10) when running OpenACS  
> (5.1.5).
>
> When monitoring (with “top” or “atop”) the memory used by Aolserver  
> running an OpenACS based Web application it is possible to notice  
> that the value of virtual memory allocated by the “nsd” process  
> always grows and never ever gets smaller.
>
>
>
> I suspected this continuous growth of the allocated virtual memory  
> was due either to tDOM or the Aolserver memory allocator. I made  
> sure in my application that every time tDOM is used its allocated  
> memory gets explicitly released, but still no luck… So I guess the  
> problem could reside in the Aolserver memory allocator.
>
>
>
> Any clue, any suggestion?  Am I doing something wrong?
>
>
>
> I’d like not to be forced to schedule a nightly restart of the  
> server just to keep the memory allocation problem under control.
>
>
>
> Thanks in advance for your help,
>
> Maurizio
>
> -- AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to  
> <listserv@listserv.aol.com> 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 <listserv@listser
v.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
 field of your email blank.

[ Post a follow-up to this message ]

Thanks a lot Janine.



Cheers,

Maurizio





From: AOLserver Discussion [mailto:AOLSERVER@LISTSERV.AOL.COM] On Behalf
 Of
Janine Sisk
Sent: 09 March 2007 20:06
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Memory problem with Aolserver/TCL/OpenACS



We had a site that was doing this, and the fix in this post worked for us:



http://dossy.org/archives/000108.html



It was rather perplexing;  only one of our many hosted sites had the
problem, and it just started exhibiting it one day with no obvious change to
account for it.  Based on Dossy's description that shouldn't be possible.



janine



On Mar 9, 2007, at 1:38 AM, Maurizio Martignano wrote:





Dear all,

I've got a question (possibly a newbie's one) on the memory
allocated by Aolserver (4.0.10) when running OpenACS (5.1.5).

When monitoring (with "top" or "atop") the memory used by Aolserver running
an OpenACS based Web application it is possible to notice that the value of
virtual memory allocated by the "nsd" process always grows and never ever
gets smaller.



I suspected this continuous growth of the allocated virtual memory was due
either to tDOM or the Aolserver memory allocator. I made sure in my
application that every time tDOM is used its allocated memory gets
explicitly released, but still no luck. So I guess the problem could reside
in the Aolserver memory allocator.



Any clue, any suggestion?  Am I doing something wrong?



I'd like not to be forced to schedule a nightly restart of the server just
to keep the memory allocation problem under control.



Thanks in advance for your help,

Maurizio

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listserv@listserv.aol.com> 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
<listserv@listserv.aol.com> 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 <listserv@listser
v.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
 field of your email blank.

[ Post a follow-up to this message ]