HotRodServer startup fails when its record cannot be inserted into topology cache

When the HotRodServer starts it inserts its record to __hotRodTopologyCache (HotRodServer.addSelfToTopologyView(...)).
However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message.