Assertion on cvs head

[Stephan Jaeger]

On Fri, 2007-08-03 at 15:48 -0400, Alan DeKok wrote:
> Stephan Jaeger wrote:
> > Here is the output of -fxxx|grep Thread
> > 
> > thread settings, just for testing:
> > start_servers = 2
> > min_spare_servers = 0
> > max_spare_servers = 0
> 
>   Oh.  That's a corner case that probably isn't well tested.  Setting
> the minimum spare threads to zero isn't nice.  It means that you have
> *no* threads available when the server is idle.  i.e. it tries to delete
> ALL threads when all threads are idle.

That was just for testing, here is output with:

start_servers = 15
min_spare_servers = 5
max_spare_servers = 10

Fri Aug  3 22:06:54 2007 : Debug: Thread spawned new child 1. Total
threads in pool: 1
[...]
Fri Aug  3 22:06:54 2007 : Debug: Thread spawned new child 15. Total
threads in pool: 15
Fri Aug  3 22:06:54 2007 : Debug: Thread pool initialized
Fri Aug  3 22:06:54 2007 : Debug: Thread 1 waiting to be assigned a
request
Fri Aug  3 22:06:54 2007 : Debug: Thread 15 waiting to be assigned a
request
Fri Aug  3 22:06:56 2007 : Debug: Threads: total/active/spare threads =
15/0/15
Fri Aug  3 22:06:56 2007 : Debug: Thread 1 got semaphore
Fri Aug  3 22:06:56 2007 : Debug: Thread 1 handling request 0, (1
handled so far)
Fri Aug  3 22:06:56 2007 : Debug: Thread 1 waiting to be assigned a
request
Fri Aug  3 22:07:01 2007 : Debug: Threads: deleting 1 spare out of 5
spares
Fri Aug  3 22:07:01 2007 : Debug: Thread 2 got semaphore
Fri Aug  3 22:07:01 2007 : Debug: Thread 2 exiting...
Fri Aug  3 22:07:06 2007 : Debug: Threads: total/active/spare threads =
14/0/14
Fri Aug  3 22:07:06 2007 : Debug: Threads: deleting 1 spare out of 4
spares
Fri Aug  3 22:07:06 2007 : Debug: Thread 3 got semaphore
Fri Aug  3 22:07:06 2007 : Debug: Thread 3 handling request 1, (1
handled so far)
Fri Aug  3 22:07:06 2007 : Debug: Thread 3 exiting...
Fri Aug  3 22:07:06 2007 : Debug: Thread 4 got semaphore
Fri Aug  3 22:07:06 2007 : Debug: Thread 4 waiting to be assigned a
request

Same assertion...

Stephan Jaeger
-- 
Stephan Jaeger <stephan.jaeger at ewetel.de>