No, I just mean something that allows differentiating between the same channel numbers in use on different connections, as opposed to something that really identifies the TCP connection.
Host:port has the potential to be very long, and has additional issues such as changing due to failover occurring etc etc, which would require updating the thread names after the fact. I'm not really looking to get into that, so much as provide a means to separate one connection from another, wherever it may be connected. In this case I just added (missed the commit?) a long value that is incremented with each new AMQConnection instance created, and is logged (at debug, could make it info?) along with the connection URL provided (which includes user, and any host:port combinations provided for failover) to allow at least some path for further identification.
The new names are currently e.g Dispatcher-Channel-1-Conn-1. I guess Channel (and now Conn) is a little redundant I guess, I just left the qualifiers because it makes it easier to distinguish what each number is what without looking up the code. "Dispatcher-1-Conn-1" instead perhaps?