You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2022/02/25 17:44:00 UTC
[jira] [Updated] (AMQ-8515) FailoverTransport should specifically handle MaxFrameSizeExceededException
[ https://issues.apache.org/jira/browse/AMQ-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Pavlovich updated AMQ-8515:
--------------------------------
Summary: FailoverTransport should specifically handle MaxFrameSizeExceededException (was: Failover should specifically handle MaxFrameSizeExceededException)
> 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
--
This message was sent by Atlassian Jira
(v8.20.1#820001)