Yes and no. ;)

Technically everything in the configuration file is a Tcl command
(ns_section, ns_param, etc.) so it's really not that much of a stretch. But
I agree, it is different.

Here's the deal, a decision was made a while back to try some new things
with AOLserver 4.5, some of which we knew wouldn't be backwards compatible.
Thread pools and limits are two pretty radical changes that were made to the
core.

Had we ever actually gotten around to deploying AOLserver 4.5 internally
here at AOL, I'm sure we would have at least done the work to provide some
backwards compatibility wrappers for things like this, but as yet we
haven't.

I'll try and update the default configuration file with some examples soon.
Sorry for the confusion.

- n



On 8/1/07, Tom Jackson <[EMAIL PROTECTED]> wrote:
>
> Nathan,
>
> This has to be the most bizzar change to the configuration setup for
> AOLserver, is it really true? Now you have to execute commands inside the
> config file to set this?
>
> Since some have called for examples, would it be possible for the author
> of
> these changes to provide a few. I have been using the threadpool
> configuration as shown in this example (start at server.tcl, then source
> threadpool files):
>
> From: <http://rmadilo.com/m2/servers/rmadilo/config/>
> # threadpool-default.tcl
> # Single Threadpool
>
> # pool = default
>
> ns_section "ns/server/${server}/pool/$pool"
> ns_param   maxconnections    100
> ns_param   minthreads        4 ;# 0
> ns_param   maxthreads        10
> ns_param   threadtimeout     120
> ns_param   map               "GET /"
> ns_param   map               "POST /"
>
>
> tom jackson
>
> On Thursday 26 July 2007 08:53, Nathan Folkman wrote:
> > You'd actually want to do it by adding the following to the end of your
> > configuration file:
> >
> >     ns_pools set procsmsgmgr -maxconns 100 -maxthreads 20 -minthreads 10
> > -timeout 10
> >     ns_pools register procsmsgmgr server1 POST /proc/msgmgr
> >
> > You can then verify that everything worked via the AOLserver control
> port:
> >
> >     server1:nscp 1> ns_pools list
> >     procsmsgmgr default error
> >
> >     server1:nscp 2> ns_server threads procsmsgmgr
> >     {min 10} {max 20} {current 10} {idle 10} {stopping 0}
> >
> >     server1:nscp 3> ns_pools get procsmsgmgr
> >     minthreads 10 maxthreads 20 idle 10 current 10 maxconns 100 queued 0
> > timeout 10
> >
> > Hope that helps!
> >
> > - n
> >
> > On 7/26/07, Shedi Shedi <[EMAIL PROTECTED]> wrote:
> > > Thanks Nathan for the info. I'm trying to configure a pool but
> ns_server
> > > threads procmsgmgr returns error on server log.
> > >
> > > [26/Jul/2007:18:06:07][4968.3074280352][-conn:0-] Error: Tcl
> exception:
> > > no such pool: procmsgmgr
> > >     while executing
> > > "ns_server threads procmsgmgr"
> > >
> > > #
> > > ns_section ns/server/${servername}/pools
> > > ns_param  procmsgmgr "Message Manager Receiving Pool"
> > >
> > > ns_section ns/server/${servername}/pool/procmsgmgr
> > > ns_param map {POST /proc/msgmgr}
> > > ns_param maxconnections   100
> > > ns_param maxdropped       0
> > > ns_param maxthreads       20
> > > ns_param minthreads       10
> > > ns_param threadtimeout    60
> > >
> > > Can you tell if my configuration is correct?
> > >
> > > regards,
> > >
> > > On 7/26/07, Nathan Folkman <[EMAIL PROTECTED]> wrote:
> > > > Those parameters moved and are now controlled via the "ns_pools" Tcl
> > > > command:
> > > >
> > > > ns_pools:
> > > >         The "ns_pools" command enables configuration of one or more
> > > >         pools of connection processing threads. The pools allow
> > > >         certain requests to be handled by specific threads. This
> > > >         could, for example, ensure multiple long running requests
> > > >         don't block other short running requests.  Pools are
> selected
> > > >         based on method/url pairs similar to the mappings managed
> > > >         by the "ns_register_proc" command.  By default, all requests
> > > >         are handled by a single, unlimited, "default" pool.  There
> > > >         is also an "error" pool as described below.  Coupled with
> > > >         the new "ns_limits" command, pools can provide for
> > > > sophisticated resource management.
> > > >
> > > > See also the new "ns_limits" command:
> > > >
> > > > ns_limit:
> > > >         The "ns_limit" command enables setting various resource
> > > >         limits for specified method/url combinations. These limits
> > > >         include such items as max concurrent connections, max file
> > > >         upload size, and timeouts waiting for connection processing.
> > > >         When limits are exceeded, connections are immediately
> > > >         dispatched to a dedicated "error" connection processing
> > > >         pool to generate a quick error response. By default all
> > > >         requests share the same default limits.  Coupled with the
> > > >         new "ns_pools" command, URL-based limits can provide for
> > > >         sophisticated resource management.
> > > >
> > > > On 7/26/07, Shedi Shedi < [EMAIL PROTECTED]> wrote:
> > > > > Its 4.5.0
> > > > >
> > > > > On 7/26/07, Nathan Folkman <[EMAIL PROTECTED] > wrote:
> > > > > > What version of AOLserver are you running?
> > > > > >
> > > > > > On 7/26/07, Shedi Shedi < [EMAIL PROTECTED]> wrote:
> > > > > > > Hi
> > > > > > >
> > > > > > > Patform: suse 10.1 (2.6.16.21-0.25-default)
> > > > > > >
> > > > > > > I have configured my nsd config.tcl as below:
> > > > > > >
> > > > > > > ns_param   maxconnections  100       ;# Max connections to put
> on
> > > > > > > queue
> > > > > > > ns_param   maxdropped      0         ;# Shut down if dropping
> too
> > > > > > > many conns
> > > > > > > ns_param   maxthreads      50        ;# Tune this to scale
> your
> > > > > > > server
> > > > > > > ns_param   minthreads      20         ;# Tune this to scale
> your
> > > > > > > server
> > > > > > > ns_param   threadtimeout   30       ;# Idle threads die at
> this
> > > > > > > rate
> > > > > > >
> > > > > > >
> > > > > > > ns_server threads command shows the min as zero, max as 10.
> > > > > > >
> > > > > > > Server Threads
> > > > > > > min    0
> > > > > > > max    10
> > > > > > > current    1
> > > > > > > idle    0
> > > > > > > stopping    0
> > > > > > >
> > > > > > > I'm not sure what i'm missing here.
> > > > > > >
> > > > > > > regards,
> > > > > > > shedi
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > AOLserver - http://www.aolserver.com/
> > > > > > >
> > > > > > >
> > > > > > > To Remove yourself from this list, simply send an email to
> > > > > > > <[EMAIL PROTECTED]> with the
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > body of "SIGNOFF AOLSERVER" in the email message. You can
> leave
> > > > > > > the Subject: field of your email blank.
> > > > > >
> > > > > > --
> > > > > > Nathan Folkman
> > > > > > [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > > > --
> > > > > > AOLserver - http://www.aolserver.com/
> > > > > >
> > > > > >
> > > > > > To Remove yourself from this list, simply send an email to
> > > > > > <[EMAIL PROTECTED]> 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
> > > > > <[EMAIL PROTECTED]> with the
> > > > >
> > > > >
> > > > > body of "SIGNOFF AOLSERVER" in the email message. You can leave
> the
> > > > > Subject: field of your email blank.
> > > >
> > > > --
> > > > Nathan Folkman
> > > > [EMAIL PROTECTED]
> > > >
> > > >
> > > > --
> > > > AOLserver - http://www.aolserver.com/
> > > >
> > > >
> > > > To Remove yourself from this list, simply send an email to
> > > > <[EMAIL PROTECTED]> 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
> > > <[EMAIL PROTECTED]> 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 <
> [EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>



-- 
Nathan Folkman
[EMAIL PROTECTED]


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

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to