While working on the demo we encountered the following problem: it seems that the topology on our test Velocloud topology had changed somehow and this was triggering this bug. The problem seems that the endpoint for tunnel status returns state changes and in some cases also the data key changes. This leads to service names being created more than one time. We have to figure out, what the real semantic of the return values is and how we can figure out, which tunnels are the most recent ones currently in use.