In revs. 17790 and 17802., I inserted (for the second time) code to write a 
logging message when a message queue became over half-full. This has proven to 
be a useful debugging aid, as it shows what tasks in the system are becoming 
overloaded well before they fail.

In rev. 18604, I revised OsMsgQ so that all message queues must be provided 
with names (which are reported in the half-full warning messages).

A user reported that his logs were getting clogged with these messages, which 
ultimately resulted in XX-8356.  It turns out that certain message queues are 
used for audio processing and are intended to operate nearly full.  (This 
log-flooding is why we removed the warning messages the first time we had them!)

But since all message queues now have names, we can tell which queues are used 
in this manner.  Rev. 18804 adds an optional argument to the OsMsgQ constructor 
to suppress the warning messages, for queues that are used in this manner.  
Currently, there is only one queue with this treatment:  mMsgqFrames in 
StreamQueueingFormatDecoder.

All of these changes are merged into 4.2 in rev. 18806.  I would like to have 
the latest versions of this code in 4.2, as it will assist in diagnosing 
problems we see in the field.  The alternative is to remove the warning message 
entirely; in 4.2 this would mean reverting 18806, 17802, and 17790.

So please:

1) Watch for messages like "OsMsgQShared::doSendCore message queue 
'AudioStream' is over half full - count = 801, max = 1600".  If this is normal 
for the queue in question, the constructor for the OsMsgQ (typedef'ed from 
OsMsgQShared) should have its reportFull argument set to 'false'.

2) Review rev. 18806 in 4.2.  Most of the changes are adding names to OsMsgQ 
constructors; the important changes are in the OsMsgQShared class in 
sipXportLib.

Dale
_______________________________________________
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/

Reply via email to