Re: [ecf-dev] service discovery working even if port mis configured

[Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx>]

Hi,

> Hopefully this will get you well on the way.   At some point in the 
> future...if desired...I could probably refactor and move the 
> EDEFBundleGenerator into ECF API rather than test code, but this can't 
> happen right away as we are closing in on Luna freeze).
using a static edef xml file I have a working environment now.

little pitfall was to strip down the edef xml file to the bare minimum 
and especially replacing the numeric id for endpoint.id from the 
examples with ecftcp://localhost:8889/server.

Before investing into the "dynamic edef" approach: how to trigger a 
rediscovery of services?
Stopping and starting the bundle with the edef programmatically should 
work but seems a bit odd...

When stopping the host there is an unbind event on the client, but when 
restarting the host there is no new bind event.
For our use case it would be a requirement to trigger a reconnect if the 
connection gets lost.

I've tried the zookeeper discovery in standalone mode and I see that the 
client is trying to reconnect to the server when the connection is lost 
and reconnects when the server is up again.

So maybe that's the way to go for us?

Bonus Question: when starting (only) the host with zookeper and using 
"centralized" for the zoodiscovery.flavor, there are error messages (for 
the host) which seem to come from a client trying connect.

WARN  [ClientCnxn] Session 0x0 for server null, unexpected error, 
closing socket connection and attempting reconnect

Whats the reason and/or background for that behavior?

Thanks!

Regards,
Peter