Hi Peter,
More from theseasonal djinn…
So, I had a littlemore patience with River 3.0’s unadorned
LookupDiscoveryManager,and it did indeed recognised the existence of an already
running 3.0djinn, but only after a fashion. River 2.3.3’sLookupDiscoveryManager
recognises the same djinn
Thanks Bill,
I suspect the thread bug was fixed in 3.0.1, are you able to confirm?
I think I can provide a fix for sluggish discovery.
One of the changes with River 3.0 was to remove instances of unsafe
publication, that is allowing a reference to "this" to escape during
object construction.