Re: [reSIProcate-users] Client Hangs in UAS mode coming from Remote But Not Local Peer
Trimming and re-sending.
So, the bit where it says "TU summary: 4" indicates that there are 4
messages waiting in the TU's (ie, DUM's) fifo. Also, note the absence
of the usual logging coming out of DUM. Now, this could be because of
a deadlock somewhere, or maybe your app stopped calling
ProcessMessages() for some reason (maybe an exception made it up to
your main loop?).
Best regards,
Byron Campen
Does that mean the following loop is my application is not
processing the messages in queue?
void ProcessMessages()
{
if (!uacShutdownHandler->dumShutDown)
{
while(dumUac->process());
}
}
Is that evident from the following log file line? What does it read
btw?
TU summary: 4 TRANSPORT 0 TRANSACTION 0 CLIENTTX 0 SERVERTX 1 TIMERS 0
-ali