[Spread-users] problem re-using private names with 3.17.0

[George Schlossnagle]

I've witnessed this behavior in the past.  I believe the problem is that 
when you call SP_disconnect(), the actual disconnect and deregistration 
in the ring is asynchronous.  So you call SP_disconnect, exit your 
process (or thread or what have you), and then immediately reconnect 
with the same name, the disconnect hasn't been processed by the ring yet.

Especially when I was running the high-latency rings at CCI this was 
constantly happening.  Sometimes it would take 30-60 seconds for a 
disconnect to be fully propogated so that a new join on the same private 
name could occur.


On Sunday, October 27, 2002, at 01:53 PM, Yair Amir wrote:

> Hi Daniel,
>
> Daniel> Hey Jeremy.  I can't say that I see the preventing of the use 
> of the
> Daniel> same private name by multiple clients as a "bug" (of course I 
> could
> Daniel> easily be wrong here ;), but I can suggest a work around.  Pass 
> a NULL
> Daniel> name to the Spread daemon when you call SP_connect() -- the 
> daemon
> Daniel> will generate and assign your client's connection a private 
> group.
>
> That was my first reaction to Jeremy's message.
> However, reading it more carefully, you see that he means
> that Spread does not allow him to use the same private name
> AFTER the previous process that used the name already disconnected.
>
> If this is true, it is definitely a bug. I know Jonathan
> is looking into this.
>
>    Cheers,
>
>    :) Yair.
>
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>
// George Schlossnagle
// Principal Consultant
// OmniTI, Inc          http://www.omniti.com
// (c) 240.460.5234   (e) george at omniti.com
// 1024D/1100A5A0  1370 F70A 9365 96C9 2F5E 56C2 B2B9 262F 1100 A5A0