Reconnection deadlock issue

We found that the reconnection code is not surrounded by a background task, 
thus causing the application to be suspended in the middle of reconnection.
The library enters deadlock after running for ~5 hours. From the logs:
STACK_DISCONNECTED event is triggered, but reconnection does not take place. 
The library's thread is busy waiting for something, and therefore does not post 
the notification which should tell the application to reconnect.
The library's status remains CONNECTED, and is not updated.
Enter and place a call to see if the library is truly locked.
The application freezes instantly upon dialling. We believe the library is 
unresponsive at this point.
To solve this, we tested moving the library calling code to a separate thread 
than the main thread, and it seems to have fixed the problem, but only 
intermittently.
There are 2 types of deadlock we have been able to reproduce; please see logs 
attached. Thanks again for all your help.

Original issue reported on code.google.com by boss...@yahoo.fr on 26 Mar 2014 at 11:56

Attachments:

[dead lock all thread (iPad).txt](https://storage.googleapis.com/google-code-attachments/idoubs/issue-172/comment-0/dead lock all thread %28iPad%29.txt)
[dead lock all thread 2 semaphore.txt](https://storage.googleapis.com/google-code-attachments/idoubs/issue-172/comment-0/dead lock all thread 2 semaphore.txt)
[dead lock all threads.txt](https://storage.googleapis.com/google-code-attachments/idoubs/issue-172/comment-0/dead lock all threads.txt)

DoubangoTelecom / idoubs

Reconnection deadlock issue #172