You can easily bind to more than one port/IP address, however, I
believe all requests in 3.x are dumped into a common connection queue,
which does not solve the original problem. It sounds like you want
multiple connection queues, so that one can be overloaded yet the
other is still getting serviced regularly. That doesn't seem possible
in 3.x to my knowledge, at least not without hacking.
Jim
>
> You definitely can do this in AOLserver 4 by loading more than one nssock
> module.
> In AOLserver 4 if you are using the built in 'virtual server' support, you
> configure one global nssock and it listens on whatver port you configure it
> to.
>
> You can then have an individual virtual server (within the same nsd process)
> listen to a different port by giving it its own server specific nssock
> module.
>
> Whether this is possible with AOLserver 3.x I don't know.
> Try looking in the list archives
>
>
>
> You could try something like this to get it to listen on port 8080:
>
> ns_section ns/server/$servername/module/nssock8080
> ns_param hostname $hostname
> ;# This is not the same as your hostname
> ns_param address $address
> ;# This is not the same as your host addr
> ns_param bufsize [expr 16 * 1024]
> ;# IO buffer size
> ns_param rcvbuf 0
> ;# Use OS defaults
> ns_param sndbuf 0
> ;# Use OS defaults
> ns_param socktimeout 30
> ;# Connection timeout
> ns_param sendwait 30
> ;# Timeout for sending of data
> ns_param recvwait 30
> ;# Timeout for receiving data
> ns_param closewait 2
> ;# Timeout for closing socket
> ns_param keepwait 30
> ;# Keepalive inactivity timeout
> ns_param backlog 5
> ;# 5 pending connections
> ns_param port 8080
> ;# Port for HTTP (typically 80)
> ns_param location ""
> ;# URL for auto-redirects (trailing slash)
> ns_section ns/server/${servername}/modules
> ns_param nssock8080 ${bindir}/nssock${ext}
>
>
>
> > -----Original Message-----
> > From: AOLserver Discussion
> > [mailto:[EMAIL PROTECTED] Behalf
> > Of Scott Laplante
> > Sent: Monday, November 03, 2003 9:36 PM
> > To: [EMAIL PROTECTED]
> > Subject: [AOLSERVER] nsd binding to > 1 port?
> >
> >
> > I'm interested in specifics regarding whether AOLServer can
> > bind itself to
> > more than one port at a time.
> >
> > Specifically, we would want connection threads bound to port 80, and
> > internal communication threads (i.e. event messages between
> > servers in the
> > cluster) bound to port 8080 (or similar).
> >
> > Our internal messages among different servers in our cluster
> > are currently
> > having to wait for a free connection thread, and in times of
> > high traffic,
> > this backup causes rather critical problems.
> >
> > Other solutions/suggestions are quite welcome, right now
> > we're trying to
> > figure out if this is possible in AOLServer 3.4 (upgrading is
> > not an option
> > at this point but if that would solve it, i would like to
> > hear that fact)
> >
> > Great thanks in avance for any information you have,
> > Scott LaPlante
> >
> >
> > --
> > 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.
