Re: [Fwd: [Kannel 0000080]: bearerbox runs out of thread when smsbox connections are sequentially established and dropped]

Hi list,

this bug has been (partly) fixed, see Mantis entry.

The main problem was that the list_consume() of the incoming list
would block the sender thread forever, because there would be still
producers that have not unregistered.

Now the receiver thread will remove a producer from the incoming list,
causing the list_consume() call to unblock and hence shutdown the
sender thread and then the receiver thread too.

The remaining problem is, when several smsboxes are connecting
simultaniously, then all boxc thread will be blocked, until the *last*
smsbox connection disconnects or breaks. Because then the
list_consume() will unblock after all producers are gone.

But I consider this as a not to heavy impact, because the sequential
connect, disconnect problem is more worst in spawning threads for any
incoming connection.

A still existing impact *may* be with the scenarios, when both
situations apply, ie. several simultanious initial smsbox connections
and then (while those keep connected) running heavy sequential
connect/disconnects.

I have to test this.

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are