[Vortex] vortex_channel_wait_reply deadlocks until vortex_connection_new is called on remote

[Jens Alfke]

On 2 May '08, at 4:55 PM, Chris Yourch wrote:

> 3)     Remote calls vortex_connection_new() during MSG frame  
> processing to connect to the local machine using a different channel.

It's opening a new _connection_, not a new channel? That seems odd;  
usually there's no need for an application to open multiple BEEP  
connections to the same peer, since BEEP already lets you multiplex  
using channels.

> 4)     vortex_connection_new() hangs for a while.  
> vortex_connection_new() stops hanging when the  
> vortex_channel_wait_reply() call on the local machine times out.

I would guess that you're using the synchronous mode of  
vortex_connection_new, and that the local peer's client code is  
getting stuck responding to the incoming connection request while it's  
still blocked waiting for the reply to the message. You'd have to  
examine the stacks on the local machine (and turn on logging) to  
figure out what's going on.

—Jens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1875 bytes
Desc: not available
Url : http://lists.aspl.es/pipermail/vortex/attachments/20080502/67516917/attachment.bin