[
https://issues.apache.org/jira/browse/AMQ-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500212#comment-17500212
]
ASF subversion and git services commented on AMQ-8515:
------------------------------------------------------
Commit 9db5f436cfa1a332f1dbd8e0f6a0563b5c1cab60 in activemq's branch
refs/heads/activemq-5.16.x from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9db5f43 ]
[AMQ-8515] FailoverTransport should handle MaxFrameSizeExceededException (#785)
(cherry picked from commit 094dbc89f3630691f1bd66d0d07fe879842fa51b)
> FailoverTransport should specifically handle MaxFrameSizeExceededException
> --------------------------------------------------------------------------
>
> Key: AMQ-8515
> URL: https://issues.apache.org/jira/browse/AMQ-8515
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.16.4
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 5.17.0, 5.16.5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)
