Issue

• We are observing the following errors intermittently on the client side when restarting broker instances in the network. It appears that
  under some conditions the set of FailoverTransport URIs becomes empty and is not replenished from via multicast discovery mechanism.
  The client is using the ActiveMQ libraries provided with JBoss A-MQ 6.1 release and multicast discovery using the following URL.
  discovery:(multicast://IP:port?group=xyz)
  The error observed in the client logs are as follows. After the initial attempt the client keeps looping over the empty set of URIs it
  appears.

WARN  2015-07-20 17:27:58,921 org.apache.activemq.transport.failover.FailoverTransport: Transport 
failed, reason:  , attempting to automatically reconnect
java.io.EOFException
    at java.io.DataInputStream.readInt(Unknown Source) ~[?:1.7.0_72]
    at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258) ~[?:?]
    at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[?:?]
    at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[?:?]
    at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[?:?]
    at java.lang.Thread.run(Unknown Source) [?:1.7.0_72]
WARN  2015-07-20 17:28:04,109 [ActiveMQ Task-3] org.apache.activemq.transport.failover.FailoverTransport: Failed to connect to [] after: 10 attempt(s) continuing to retry.