No the connection will not be cut just because the lease expires. It *might* be cut if the reason the lease has expired is because connectivity with the service is lost (for whatever reason) such that comms is impossible with the LUS to extend the lease and impossible to talk to your client.
I think it's worth explaining that the lease renewal with the lookup service is to help it figure out when a service has expired so it can cleanup. If your clients also need such a method there probably ought to be some protocol supported via the service API to test liveness (e.g. a simple ping method). Note also that the lease maintained with the lookup service should be short but is intended to be repeatedly renewed to indicate the service that registered is still alive. On 25 November 2011 16:44, Vladimir Ghetau <[email protected]> wrote: > Good evening, > > I am currently building an app which requires that all services are up and > running. > > Every 5 minutes, I want to check if a service is still up and running. > > The clients may send over big streams of data, could be as big as 4GB, > which may take more than 10 minutes of transfer over the network. > > This means, that by the time the data transfer finishes, the lease already > expired. > > My question is: > > Will the connection with the service be cut when the lease is discarded by > the lookup service? > > Many thanks for the help, > Vladimir Ghetau >
