Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added automaticTopologyRecovery to Fs2RabbitConfig #972

Merged
merged 3 commits into from
Sep 4, 2024

Conversation

SheliakLyr
Copy link
Contributor

TopologyRecovery feature in amqp-client is sometimes strange. I prefer to have it disabled. This PR adds the needed configuration option to Fs2RabbitConfig.

This change is not backwards compatible in Fs2RabbitConfig constructor. It is not possible to add a default - only one apply method can have defaults defined. I could try to add some additional methods to keep compability.

Also, I fixed a small compilation error (unrelated).

@@ -57,6 +58,7 @@ object Fs2RabbitConfig {
internalQueueSize: Option[Int],
requestedHeartbeat: FiniteDuration = FiniteDuration(ConnectionFactory.DEFAULT_HEARTBEAT, TimeUnit.SECONDS),
automaticRecovery: Boolean = true,
automaticTopologyRecovery: Boolean = true,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the default value for the java library, I suppose, is it not?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, in "modern" versions of that library.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, I mean - the one we are using in fs2-rabbit at least

@geirolz
Copy link
Collaborator

geirolz commented Sep 3, 2024

This change is not backwards compatible in Fs2RabbitConfig constructor

This isn't a problem I'd say

@geirolz
Copy link
Collaborator

geirolz commented Sep 3, 2024

P.S. Ignore the CI error, there is a PR to fix it and it isn't related to your changes
#973

@geirolz geirolz merged commit 11024d0 into profunktor:master Sep 4, 2024
2 of 3 checks passed
@geirolz geirolz added this to the 5.3.0 milestone Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants