I was trying one server. From the traces I saw that SASL authentication was
successful. Then there was attempt to bind to a resource, but server did not
respond with OK or error. I was told that the server was "down". I don't
understand their setup that SASL was done, but the rest was not responding.
Bogdan
-----Original Message-----
From: Jakob Schroeter [mailto:js@xxxxxxxxxx]
Sent: Thursday, July 19, 2007 8:09 AM
To: gloox-dev@xxxxxxxxxx
Subject: Re: [gloox-dev] Lock
On Thu Jul 19 2007, Bogdan wrote:
> Sometimes I'm getting in scenarios where send (protected by a mutex) is
not
> returning forever. This is cased by misbehaving server for instance. Next
> interaction with gloox hangs since the mutex is not released.
What do you mean by 'misbehaving server'?
> Have you seen this problem?
Not yet.
cheers,
Jakob