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 immediately.
Also noted was atermination concern with 3.0’s LookupDiscoveryManager, which
keepthreads
sun.misc.Launcher$AppClassLoader@blah_thread-0,and Thread-1 (?)
running permanently.
The former is a bitof a bind, but the latter can be worked around with a system
exit of0, much as must be done in QA.
Kind regards,
Bill
On Sunday, December 10, 2017, 7:01:49 AM GMT, Peter <j...@zeus.net.au>
wrote:
Hi Bill,
Are you trying to discover a lookup service provided by River 2.2.X?
Which version of discovery are you using? V2 is now enabled by default
in 3.0.X, you won't discover any V1 lookup services unless you enable it
by passing in a ConstrainableLookupLocator using InvocationConstraint
with DiscoveryProtocolVersion.ONE to LookupDiscoveryManager's constructor.
If you're still using V1, I'd suggest using LookupLocators to support
both discovery versions 1 and 2, which should allow you to migrate off
version 1.
Version 1 discovery has been deprecated and will likely be removed in a
future version of River, for now at least, it can still be re-enabled.
If this isn't the cause, can you enable the loggers for LookupDiscover
and LookupDiscoveryManager and send us the output?
Regards,
Peter.
On 9/12/2017 11:42 PM, bill pickup wrote:
> Hi all. Season’s greetings… well, almost.
> Apologies for coming over the dev@ wire, but the user@ wire seems to be
> defunct. Anyway, I’m designing something for River, so I don’t feel too bad.
> I’m having problems with LookupDiscoveryManager in 3.0.0 and 3.0.1. My call
> is simple,
> new LookupDiscoveryManager(LookupDiscovery.ALL_GROUPS, null,
>(DiscoveryListener) this);
> but this refuses to discover anything. However, it works in 2.2.3, for the
> same djinn.
> Is something broken?
>
> Kind regards,
> Bill
>
