Hello everyone,

I have been able to solve the problem. Up to now I have been using
default values for threads for my server. It seemed that they were not
enough.

We have not had a big increase in the hits to our site, so I think the
problem started when we increased the connections to the DB per
AOLServer process (from 4 to 20).

What we have done now is to put minthreads in 5 and maxthreads in 20,
and now everything works like a charm. No locked threads. Every thread
servers the requests very fastly.

If someone knows why did this problem happen or have a guess, it'd be
nice to know it, just for future reference.


Kind Regards,

  Juan José



-  
Juan José del Río    |  Comercio online / e-commerce
(0034) 616 512 340   |  [EMAIL PROTECTED]


Simple Option S.L.
  Tel: (0034) 951 930 122
  Fax: (0034) 951 930 122
  http://www.simpleoption.com


On Mon, 2008-02-04 at 16:50 +0100, Juan José del Río [Simple Option]
wrote:
> Hello,
> 
> Since two days ago, I have been experiencing weird problems with
> AOLServer. Maybe someone of you have a clue of what's going out exactly.
> 
> I will detail my problem in the easiest way possible.
> 
> 1. A user requests a page
> 2. His browser sends the request
> 3. The browser waits for AOLServer's reply showing "Waiting for
> <servername>..."
> 
> 
> 4. Another user requests a page
> 5. His browser sends the request
> 6. AOLServer serves the 1st request
> 7. AOLServer serves the 2nd request
> 
> 
> Excerpt from my logs:
> 
> 192.168.1.193 -  [04/feb/2008:16:39:07 +0100]
> "GET /ayuda/informacion-devoluciones.adp HTTP/1.0" 200 7521 "" ""
> 4.494904
> 
> 192.168.1.193 - - [04/feb/2008:16:39:08 +0100] "GET / HTTP/1.0" 200
> 15474 "" "" 0.187405
> 
> 
> I ask for the page "/ayuda/informacion-devoluciones.adp" around 16:39:03
> but AOLServer doesn't return it until around 16:39:08 i ask the front
> page (any other page works too). Note that aolserver counts that the 1st
> page took around 4.5 seconds to be served... considering that it's a
> pretty static page, that should be served in much less than 150ms.
> 
> 
> I found a way to fix this. I simply run this script:
> 
> while [[ 1 ]]; do
>       lynx -source http://mysite > /dev/null ;
>       sleep 1;
> done
> 
> 
> and that way I will always have requests, so the delay will be under 1
> second for the incoming requests.
> 
> 
> Has anybody a clue about what is going on?
> 
> 
> Thanks in advance,
> 
>   Juan José
> 
> 


--
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