Just another guess: do you have anything between AOLServer and the connections, such as Apache proxy and other things? Most performance problems in AOLServer we've seen are related to the environment, no to the AOLServer itself.
2009/5/1 Dossy Shiobara <do...@panoptic.com> > On 5/1/09 6:17 PM, William Scott Jordan wrote: > >> I think it's worth noting that when AOLserver stops accepting >> connections, nslog doesn't log any of the failed requests. New >> connections seem to just be rejected outright. >> > > Do you have nscp enabled? Is the control port still responsive to > commands? Can you capture the output of "join [ns_info threads] \n" from > the control port once AOLserver stops accepting connections? > > -- > Dossy Shiobara | do...@panoptic.com | http://dossy.org/ > Panoptic Computer Network | http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to < > lists...@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 <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
