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

RabbitMq configuration - mq cluster support #7876

Closed
catwarrior opened this issue Feb 28, 2021 · 1 comment · Fixed by #7897
Closed

RabbitMq configuration - mq cluster support #7876

catwarrior opened this issue Feb 28, 2021 · 1 comment · Fixed by #7897

Comments

@catwarrior
Copy link

Documentation

Please check the official documentation before asking questions: https://docs.abp.io

GitHub Issues

GitHub issues are for bug reports, feature requests and other discussions about the framework.

If you're creating a bug/problem report, please include followings:

  • Abp version3.2.1.

With RabbitMQ.Client, we can connect to a MQ cluster.

    var connectionFactory = new ConnectionFactory()
    {
          UserName = "guest",
          Password = "guest"
    };  
    var connection = connectionFactory.CreateConnection(new string[] {
    "192.168.23.149",
    "192.168.23.144",
    "192.168.23.143"
     });
     var channel = connection.CreateModel(); 

But in abp configuration, it's only support something like this,

{
  "RabbitMQ": {
    "Connections": {
      "Default": {
        "HostName": "192.168.23.149",
        "Port": "5672"
      }
    }
  }
}

How to acheive it?

@catwarrior
Copy link
Author

catwarrior commented Feb 28, 2021

looks like in Volo.Abp.RabbitMQ.ConnectionPool Get Method, it use ConnectionFactory.CreateConnection() hardcoded,
it would be better if we can change to use ConnectionFactory.CreateConnection(hostnames[])

https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.RabbitMQ/Volo/Abp/RabbitMQ/ConnectionPool.cs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants