Added:
Extra log message to MqttEndPoint.mqttConnect()
Changed log level on message in ConnectionManagerService
Changed autodiscovery timeout default to 65 seconds from 10mins
Improve support for re-opening sockets when network errors detected.
Corrected update SQL for Node/IP mapping updates.
Fixes to node registration to handle update versus insert, and improved
logging when errors detected.
Improved message when service handlers cannot be found. Now includes the
name of the class reporting the error -- this is important to know if it
is a client dispatcher (where such errors are usually much less
important) versus the Fabric Manager dispatcher.
Bug in update sql string creation for NodeNeighbour table
Raise a message to Info level to clearly indicate successful connection
and tidy up another log message
When an endpoint is lost we should set that neighbour to unavailable in
the registry
eclipse launcher uses build in fabric.build project
Neighbours marked unavailable due to MQTT issues must be removed from
the Discovery cache to enable rediscovery and reconnection attempts.
Discovery Listeners copig with connection failure, trying to restablish
at regular intervals  at regular intervals
Change a default timeout value
Now ignores loopback interfaces as these aren't of value to node
discovery.
Fix so discovery multicasts will restart after a network failure
Merge branch 'master' of https://github.com/edgware/edgware.git
Added logic to cope with reconnecting to a different network
Fixing Windows Run as Service things
tidier code
DistributedPersistence not picking up node specific config, needs to do
this after registry is connected and Node has been intialised
Tidying up readme and logging for Running Edgware Components as services
on Windows