On Fri, 2011-04-29 at 11:16 -0400, Worley, Dale R (Dale) wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Joegen Baclor > [[email protected]] > > So I think the safest move (might not be the most elegant) is > to preserve the status quo and just get rid of the nasty queue is full > error message. > _______________________________________________ > > I hope you don't mean to prevent queue full situations from being logged. > There is a *reason* we put > that message in: If a queue fills and chokes the process so it doesn't do > any useful work, then there > is some way to determine *which* queue filled, and thus, which thread has > gotten blocked, so we have > some hope of finding and solving the problem. >
No the queue this way is managed in correct way. The problem is in the sentence "preserve the status quo" what i mean is: in the SipUdpServer the status quo is -> sending events for gc and run gc each time in the SipTcpServer the status quo is -> ignore events for gc In my first solution I move SipTcpServer to work like the Udp one and start managing request for GC In the other one i follow the suggestion from Joegen and disalbe the sending of event (for both servers) this is the point _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
