Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MassTransit 6.2.4. RabbitMQ. The regression in UseCluster() with the custom SSL settings or the default port.
See original GitHub issueThe change introduced with the https://github.com/MassTransit/MassTransit/issues/1784 change not only removed the ClustersMembers property from the IRabbitMqClusterConfigurator interface but introduces a regression in the nodes connection configuration.
Before the 6.2.4 (in 6.2.3 at least), the SSL settings (as well as port) were propagated to the instance of AmqpTcpEndpoint from the global settings during the invocation of the ConnectionFactory.CreateConnection.
We the replacement of the EndpointResolver we now always using the default SSL settings and have no way to override it in the configuration.
Also, it’s better to consider bumping the minor version with such a set of changes:
- Removal of the configuration property without deprecation.
- Changing of the behavior for the port propagation.
- Changing the behavior of the SSL settings propagation.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@phatboyg Both issues seem to be resolved with the provided fix. Thanks for so fast response!
Once the develop packages are built, you’re welcome to test it out and verify it meets your requirements. I really have no way to test your scenario.