The client is initially registered with hostname, but once socket comm starts,
everything is identified strictly by IP address; this causes a double
registration of the task client, which then causes all sorts of double resource
counting, etc.
The easiest solution is to only accept IP addresses. The better solution is to
not have to convert to an IP. Not sure if that's possible - it's converted to
IP to guard against multiple NICs on a physical host.
Original issue reported on code.google.com by de...@battams.ca on 30 Oct 2010 at 3:45
Original issue reported on code.google.com by
de...@battams.ca
on 30 Oct 2010 at 3:45