[Spread-users] "Spread hanging in logging application" redux?

[Jack Repenning]

Just about two years ago:

http://lists.spread.org/pipermail/spread-users/2002-April/000705.html

... there was a discussion in this list about a Spread hang that could 
arise under certain conditions of membership or network instability.  
At that time, Yair seemed to be on the trail of an enhancement to 
repair communications after such an event, but didn't think it 
appropriate to include in the then-current release (3.16.2).  Something 
about "to have on the token another field that will report the id of 
the daemon that set the ARU and caused it to go down."  Did such a 
change make it into 3.17?  I grubbed the release notes and other email 
archives assiduously, but couldn't confirm (or deny) it.

Reason I ask: one of our sites just ran into something (once, 
non-reproducible at this point) that looks rather same-ish, running 
Spread 3.17.1.  If the fix actually did make it into 3.17, then I'm 
obviously smokin' something.  If it didn't ... can I help it along?

-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835.8090