Hi,
I've been chasing a protocol startup problem that only occurs when you
have three (or probably) more systems talking to the CMA (a total of 4
endpoints).
I'll look at it a little more tonight, but then it will have to wait
until I get back from a business trip in about 10 days - since I'm
taking one of my test machines with me on the trip.
It appears I'm being a little too simplistic in the protocol startup and
shutdown logic. Don't yet know what it is that makes it happen only
when four (or probably more) endpoints are involved - but that's
definitely the case.
Three of them are talking to the fourth one - not to each other.
I recall similar problems with the multicast heartbeat protocol. But
that's been over 10 years - and strangely enough my memory is a bit
fuzzy on that -- and this isn't a multicast protocol anyway...
I'll let you know if I figure things out.
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
