On Thu, 2009-11-26 at 12:57 +0000, Gabor Paller wrote: > Hi, > > > > I am chasing a bug in our load test and in order to find the culprit, > I left only the SipX and the load test tool in the picture. > > > > I noticed that the memory usage of SipXproxy goes up (may be just a > bug on our side) but then I found cryptic messages in the SipXproxy > debug log. > > > > "2009-11-26T12:39:08.429698Z":57132:SIP:DEBUG:kennedy.onrelay.local:SipUserAgent > > -2:B6D7EB90:SipXProxy:"SipTransactionList::removeOldTransactions > deleting 550 of > > 1026 transactions (0 busy)" > > > > Is it normal that SipXproxy has so many transactions in its > transaction table? Or does this show that we somehow mismanage the > transactions in our load test tool?
Yes this is exactly what is expected. SipTransaction objects in the code have a many-to-one relationship with an actual sip call. Such objects are used to hold dns lookup info, forking path info and other internal information. They are removed from the SipTransactionList after a timer fires. You should see the remaining 476 objects deleted at later times in the log (possibly all at once, possibly in groups.) -Kathy _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
