Better error reporting is needed when host attempts to register with a name already registered

Register a master / slave set up and leave the setup so the slave has the name 'master' the master will attempt to connect, will exchange some messages and the master DC eventually reports: -

"JBAS010832: There is already a registered host named 'master'"

The slave however keeps on trying to connect again and again eventually giving up after opening without closing 100 connections to the master DC, at no point does the error get reported to an end user to actually correct the simple mistake.