On 5 Oct 2013, at 2:32 PM, Oleg Kalnichevski <[email protected]> wrote:
>> That is, it's normal for the client to be stuck that way (like in those
>> traces), in spite of connection and socket timeouts?
>>
>
> What do you expect me to say? The threads are stuck in a native read
> method. There is no way of knowing that what exactly is going on inside
> of it. If this behavior is reproducible all I can suggest that you run
Well, I just expect it to be documented. It's a kind of surprise.
It's definitely reproducible, though, so I'll try with all the logging you
suggested--maybe we can catch it.
Ciao,
seba
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
