This shows (I think) that if you currently have N threads active, no
threads will timeout if there are N hits in threadtimeout seconds, at
least on a Linux box, because the thread scheduling is FIFO instead of
LIFO. On one of our production server, we are up to around 26 active
threads. I don't
Hi !
I was afraid that you would say to recompile ;-) I need to revise my C++!
Thanks for your help, and I will try this evening!
- Daniel
- Original Message -
From: Ariel E. Carná [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 18, 2001 3:48 AM
Subject: Re: [AOLSERVER]
Harry Moreau wrote:
Personally, I'm heartened to hear other people see leaks
Yea, me too! I have several systems where nsd 3.2+ad12 will slowly
consume memory until, if not restarted, it will crash the system. I had
been debating whether I should upgrade to 3.4 and see if it would help,
but
I was travelling yesterday, plus we are still fighting a few fires
since the 3.4 upgrade. To answer some of the questions/suggestions
people have posted:
1. Yes, I'm sure we're running 7.6 TCL. I ran into a few problems
with 8.X because we (intentionally) use poorly-constructed lists
in a
On Wednesday, October 17, 2001, at 10:23 AM, Jim Wilcoxson wrote:
We don't use nsv's - IMO that programming model is broken because
regular TCL constructs can't be used on nsv's.
I probably missed a memo or something, but can you tell me what you have
in mind here?
Pete.
proc foo {var} {
if {$var == 10} {
return 1
} else {
return 0
}
}
ns_share shvar
set shvar 10
set plainvar 20
if {[foo $shvar] || [foo $plainvar]} {
ns_return 200 text/plain had a foo
} else {
ns_return 200 text/plain no foos here
}
I realize that when calling foo I could
Try 3.3+ad13. It has a memory leak fix involving TSDs that I
back-ported from the 4.0 tree.
+-- On Oct 17, Janine Sisk said:
Yea, me too! I have several systems where nsd 3.2+ad12 will slowly
consume memory until, if not restarted, it will crash the system.
In glancing at the zippy code, it looks like it used a power-of-2
algorithm, so I figured it might cause less heap fragmentation. I
think that might be at least some of the problem. Does the standard
gnu/linux memory allocator handle fragmentation poorly/well?
+-- On Oct 17, Jim
+-- On Oct 17, Jim Wilcoxson said:
In glancing at the zippy code, it looks like it used a power-of-2
algorithm, so I figured it might cause less heap fragmentation. I
think that might be at least some of the problem. Does the standard
gnu/linux memory allocator handle fragmentation
Hi,
It would seem that 2 DLL files are missing from the Windows pre-compiled version of
AOLServer, downloaded from aolserver.com:
- nstcl.dll
- nsd.dll
If anyone has a copy of these files for AOLServer 3.4, could you please send me a copy?
Cheers,
Daniel
Janine Sisk wrote:
Harry Moreau wrote:
Personally, I'm heartened to hear other people see leaks
Yea, me too! I have several systems where nsd 3.2+ad12 will slowly
consume memory until, if not restarted, it will crash the system. I had
been debating whether I should upgrade to 3.4 and see
Hi there,
in Screen Name Service, we're currently investigating a problem regarding the
truncation/dropping of HTTP headers when they're becoming too big or too many
for the client or the server to handle.
Just wanted to ask you guys if you know of any limitations of AOLserver in
this
i'm not sure this will help but
you might try making the url that generates the pdf file end with
.pdf (if you not doing that already..)
i found that some versions of IE don't always pay attention to the content-type
but they will pay attention to the file suffix..
OK, I have pdflib going in
There are 2 MS support articles you need to read. Mike's correct in stating
IE ignores MIME type - it does a lot of second-guessing. One of the articles
deals with that:
http://msdn.microsoft.com/library/default.asp?url=/workshop/networking/monik
er/overview/appendix_a.asp
Another is in the
Ok, I must have missed something, or might have been off of the cluetrain too long,
but what exactly is 'zippy'? I did a google search, but I was getting mostly 'zippy
the pinhead' and other weird stuff!
Anyone have an URL or explanation?
thanks,
--brett
On Wed, 17 Oct 2001 09:54:25 -0500
+-- On Oct 17, Brett Schwarz said:
Ok, I must have missed something, or might have been off of the cluetrain too long,
but what exactly is 'zippy'? I did a google search, but I was getting mostly 'zippy
the pinhead' and other weird stuff!
It's the -z flag to nsd.
zippy is the -z command line option to AS. It causes an AOL-designed
memory allocator to be used instead of the standard C library malloc.
Properties of zippy are that it has separate heaps for each thread
instead of a shared heap, thus avoiding the need to lock when
malloc'ing private thread
This will probably be an issue for us in the future. Thanks for bringing it
to light.
--
Mark Hubbard: [EMAIL PROTECTED]
Microsoft Certified Professional
Never apply a Star Trek solution to a Babylon 5 problem.
-Original Message-
From: Dossy [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
+-- On Oct 17, Mark Hubbard said:
This will probably be an issue for us in the future. Thanks for bringing it
to light.
Note that if you use ns_getform, and the request was a POST with content
in multipart/form-data format, then maxpost does not apply.
+-- On Oct 17, [EMAIL PROTECTED] said:
Where is the limit, exactly? Tcl API or C API?
The limit is in the Ns_ConnGetQuery function. It does not apply to file
uploads, because those are sent in multipart/form-data format.
+-- On Oct 17, Rob Mayoff said:
The limit is in the Ns_ConnGetQuery function. It does not apply to file
uploads, because those are sent in multipart/form-data format.
More accurately, the limit is enforced by the Ns_ConnGetQuery function.
It is set using the ns/server/servername
On a test server configured with threadtimeout set to 120, minthreads
not set (defaults to 1/0 I think), and maxthreads set to 40, I have
another server reference a URL every 5 seconds. What I see on the
test server is:
[17/Oct/2001:19:17:49][9533.8200][-conn0-] Notice: monitor: returning page
OK, I have pdflib going in aolserver and it generates beautiful pdf reports. I send
them to the browser via 'ns_returnfile 200 application/pdf /tmp/pdffilename'. On some
machines it works great. On others, it does not work at all. The root of the problem
is something to do with the embed
23 matches
Mail list logo
