I'm experiencing another instance of permanent lock.
Sometimes when I shutdown my app, the disconnect() is called (by me or by
gloox when I'm not calling, it tried both cases, same effect).
In the cleanup() the mutex is waiting on MutexGuard rm( m_recvMutex );
It is not easy to reproduce it. But I'm under impression that it (most
often) happens when the connection was lost (server disconnected) and I'm
shutting down my app.
In my debugger I'm not seeing that another thread already hold the lock
(perhaps it is just hard to see it).
Perhaps it would be good to do more robust clean to "ignore" the lock.
Have anyone seen that?
Thanks,
Bogdan
-----Original Message-----
From: Jakob Schroeter [mailto:js@xxxxxxxxxx]
Sent: Tuesday, July 24, 2007 5:52 AM
To: gloox-dev@xxxxxxxxxx
Subject: Re: [gloox-dev] Lock
On Thu Jul 19 2007, Martin Acevedo wrote:
> I have a simillar problem with the file transfer when the other party
> cancels the transfer.
> I use a simple workarround to the send function, I added a timeout option
> to the socket
> with the function "setsockopt" and the parameter SO_SNDTIMEO in 5 seconds
> for example,
> but I don´t know if it has a hidden behaivor.
Have you tried using SOCKS5Bytestream::recv() with a timeout value other
than
-1?
cheers,
Jakob