[
https://issues.apache.org/jira/browse/AMQ-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-8515:
--------------------------------
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).
was:Since MaxFrameSizeExceededException extends IOException, the failover
transport handles it as a reconnect scenario, instead of re-throwing
MaxFrameSizeExceededException to the caller
> FailoverTransport should specifically handle MaxFrameSizeExceededException
> --------------------------------------------------------------------------
>
> Key: AMQ-8515
> URL: https://issues.apache.org/jira/browse/AMQ-8515
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.16.4
> Reporter: Matt Pavlovich
> Priority: Major
> Fix For: 5.17.0, 5.16.5
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
