[
https://issues.apache.org/jira/browse/AMQ-8515?focusedWorklogId=733309&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-733309
]
ASF GitHub Bot logged work on AMQ-8515:
---------------------------------------
Author: ASF GitHub Bot
Created on: 25/Feb/22 20:34
Start Date: 25/Feb/22 20:34
Worklog Time Spent: 10m
Work Description: mattrpav commented on pull request #785:
URL: https://github.com/apache/activemq/pull/785#issuecomment-1051237831
First round of tests passed clean. I pushed an update of change that
included comments in the test w/ link to the jira about how client check=false
+ failover + server check=true is an infinite retry.
I'll merge once the next round of tests goes green.
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 733309)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
