Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
[deleted comment]
[deleted comment]
oh,I see.It will deal with the queue.
But why after the flow of the above log,some udp ports will be occupied until
exit the mrcpServer.
What circumstance the mrcpServer can frequently receive 'SIP Event
[nua_i_cancel] Status'?
Original comment by chengchu...@gmail.com
on 11 Apr 2014 at 8:06
The occupied UPD ports are just a side effect of the real problem. The real
problem is in the plugin which stopped responding to the server requests
starting from
2014-04-04 09:10:28:983806 [DEBUG] Process Message [Pachira MRCP connector]
[0x10090f80;1;0]
Pay attention to the following sequence of traces.
[DEBUG] Signal Message to [Pachira MRCP connector]
[DEBUG] Process Message [Pachira MRCP connector]
[DEBUG] Wait for Messages [Pachira MRCP connector]
The statement Signal Message is logged when the server sends a message to the
plugin. The statement Process Message is logged before the plugin starts
processing of the message. And finally the statement Wait for Messages is
logged when the processing has been completed and the corresponding callback
has been returned.
For the mentioned above Process Message statement, which happened at 2014-04-04
09:10:28:983806, there was no response, neither the callback returned. All the
consecutive Signal Message requests were not been processed either.
This could happen because of a dead lock in the plugin. Or it's also possible
that the function gets into an infinite loop!
Original comment by achalo...@gmail.com
on 11 Apr 2014 at 9:28
This actually was not a defect but a request for clarification.
Original comment by achalo...@gmail.com
on 12 Aug 2014 at 1:19
Original issue reported on code.google.com by
chengchu...@gmail.com
on 10 Apr 2014 at 11:30Attachments: