[Openh323gk-developer] Re: GnuGK crash in CloseUnusedThreads()

[<ii...@bk...>]

Hello

I was check GnuGK with CallSignalHandler=4
No any difference - I have stable crash at this place.
Chance to got crash is not depend on number of
maximum call signal handlers in INI file.

Igor

> Maybe  the problem is using only one call signal handler
> to handle the load. Try to increase CallSignalHandler to
> a greater value and see if it still happens.

> ----- Original Message -----
> From: <ii...@bk...>
> Sent: Thursday, November 25, 2004 12:08 PM

>> Under high load latest 2.0x GnuGK crash.
>> We got crash every day or sometimes every 2nd day (always
>> only under high load / mean > 1E1)
>>
>> Linux RedHat9. GnuGK compiled with latest OpenH323 + latest PWLib.
>> GnuGK was in routed mode without full proxy (only
>> signaling was pass over it, no RTP channels).
>>
>> It was have around 2E1 load or 60 active calls.
>> CPU = Intel 2.4 GHz with load less then 5%.
>> RAM = 512 mb (most free).
>>
>> Nothing special in INI (CallSignalHandlerNumber=1).
>> Total minimized binary compiled with no radius, no
>> accounting, no mysql. Was used GCC version 3.3.5 for
>> compilation. CDR's was collected over 7000 port.
>> No any commands or reloads over 7000 port.
>>
>> Calls pass in GW-GW mode over single predefined in INI
>> permanent endpoint (no ARQ, no LRQ - all calls
>> was go between 2 fixed CISCO AS5300 IP's and start
>> from Q931 setup)
>>
>> Crash call stack:
>>
>> Gatekeeper::Main()
>>  Gatekeeper::HouseKeeping()
>>   H323RasSrv::Check()
>>    HandlerList::Check()
>>     ProxyHandleThread::CloseUnusedThreads() (this=0x4022c5d0) at 
>> ProxyThread.cxx:740
>>      MyPThread::Destroy() (this=0x40269bd8) at thread.cxx:56 (called from 
>> ProxyThread.cxx:761)
>>       PThread::WaitForTermination() const (this=0x40269bd8) at 
>> tlibthrd.cxx:1198
>>        PThread::IsTerminated() const (this=0x40269bd8) at 
>> tlibthrd.cxx:1183
>>         pthread_kill () from /lib/tls/libpthread.so.0
>>
>> Look like ProxyHandleThread::CloseUnusedThreads() code in not
>> thread safe. Can anybody comment how to solve this and make it stable ?
>>
>> Igor