[Vortex] vortex alive protocol
mydexterid at gmail.com
Wed Oct 6 13:10:45 CEST 2010
Ok. After some hours of investigation here's what I found:
When I started to use the alive feature, it went to an infinite loop
on this line: vortex_channel.c:8455
This happened because the incoming_msg list length was always growing
so it never reached the end.
And I think this growing happened because in vortex_alive.c there was
no vortex_channel_send_rpy, only
After I modified vortex_alive.c with the attached patch, it seems that
it is working as it should. Though I'm not
really aware of the concept, but I hope this will help you sort things out.
Pls. let me know if the concept was different from what I've modified,
and/or if you've managed to fix this.
On Tue, Oct 5, 2010 at 2:06 PM, DEXTER <mydexterid at gmail.com> wrote:
> Ohh.. a piece of information:
> the next 6 runs of this test passed ok, the 7th failed again. So this
> could be a race condition somewhere...
> On Tue, Oct 5, 2010 at 2:00 PM, DEXTER <mydexterid at gmail.com> wrote:
>> Hi Francis,
>> I'm trying to put the alive protocol in practice, and have some
>> problems with it, though it could be on our side.
>> So just to be sure I ran the test_16 regression test, and i get this:
>> INFO: running test=test_16
>> INFO: running test against localhost, with BEEP TUNNEL proxy located
>> at: localhost..
>> INFO: HTTP proxy located at: localhost:3128..
>> INFO: Checking to run test: test_16..
>> Test 16: checking alive with check-perid=20000, and unreply count=0
>> Test 16: waiting connection to be detected to be closed..
>> Test 16: Connection closed conn id=1..
>> Test 16: ok, connection close detected..
>> Test 16: checking alive with check-perid=10000, and unreply count=4
>> Test 16: expected proper channel creation while checking alive profile..
>> Test 16: Check ALIVE profile [ FAILED ]
>> is this intended? :)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1357 bytes
Desc: not available
More information about the Vortex