[Vortex] vortex_channel_wait_reply deadlocks until vortex_connection_new is called on remote

[Robert M. Münch]

On Sat, 03 May 2008 01:55:58 +0200, Chris Yourch <chris at replicus.com>  
wrote:

> I have a situation where vortex_channel_wait_reply() deadlocks because  
> vortex_connection_new() is called on the remote machine during MSG frame  
> processing.
>
> Here's the sequence of actions:
>
> 1)     Local machine sends MSG via vortex_channel_wait_reply().
> 2)     Remote machine receives the MSG.
> 3)     Remote calls vortex_connection_new() during MSG frame processing  
> to connect to the local machine using a different channel.
> 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.
>
> Any ideas on what is happening and why?

Hi, beside what Jens said regarding vortex_connection_new, what I do is to  
use an on_connect handler on the listener side that will setup a couple of  
channels from the listener to the initiator. The result is that I have a  
set of channels from A to B and a set of channels from B to A. Robert