I'd like someone to review main rev. 18617, described below. What it does is,
when SipUserAgent starts a Sip{Udp,Tcp,Tls}Server object, to start the object's
thread. Since these objects are subclasses of OsServerTask, they are intended
to have their object-threads execute, but the previous code did not start those
threads. As far as I know, all that the threads do is garbage-collect old
Sip*Client objects when one of those objects exits, and tha doesn't seem to
have functional effects under normal conditions. But under overload, we've
seen garbage-collecting fail because the object-threads weren't running.
Dale
________________________________________
From: [email protected]
[[email protected]] On Behalf Of
[email protected] [[email protected]]
Project sipXecs
New Revision 18617<http://code.sipfoundry.org//changelog/sipXecs/?cs=18617>
Committer dworley
Date 2010-04-18 17:12:49 -0500 (Sun, 18 Apr 2010)
Start the object-tasks when the Sip*Server objects are created.
Modified:
* main/sipXtackLib/src/net/SipUserAgent.cpp
<http://code.sipfoundry.org//browse/sipXecs/main/sipXtackLib/src/net/SipUserAgent.cpp?r1=18616&r2=18617>
_______________________________________
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
