Major Description
Since MaxFrameSizeExceededException extends IOException, the failover transport handles it as a reconnect scenario, instead of re-throwing MaxFrameSizeExceededException to the caller
Note: client-side maxFrameSize=false, with failover=true and server-side maxFrameSize= true results in infinite retries since the broker hard-closes the connection and the failover transport resets the 'connection failure counter' to zero upon successful reconnect (since the broker transport isn't really offline).
