是否有最佳实践来处理并发环境中跨多个通道的 RabbitMq 发布者确认?

如何解决是否有最佳实践来处理并发环境中跨多个通道的 RabbitMq 发布者确认?

我在 Asp.net API 应用程序中使用 Rabbitmq,并且已经实现了发布者确认模式。存储在 ConcurrentDictionary 中的通道和相应主体的序列号。从长远来看,我想使用多个渠道来提高性能。

我用 DefaultObjectPool 和 IPooledObjectPolicy 接口尝试了这个。这给了我一个频道,所以我尝试在每个线程上分配多个频道。 现在我遇到的问题是,我将各个通道的序列号存储在我的 ConcurrentDictionary 中,并且序列号和各个通道之间没有映射。

是否有在并发环境中跨多个渠道处理发布者确认的最佳做法?

池化对象:

public class RabbitModelPooledObjectPolicy : IPooledObjectPolicy<IModel>
{
    private readonly ILogger<RabbitModelPooledObjectPolicy> _logger;
    private readonly IOptions<RabbitMqConnectionSettings> _connectionSettings;
    private readonly IConnection _connection;

    public RabbitModelPooledObjectPolicy(ILogger<RabbitModelPooledObjectPolicy> logger,IOptions<RabbitMqConnectionSettings> connectionSettings)
    {
        _logger = logger ?? throw new ArgumentNullException(nameof(logger));
        _connectionSettings = connectionSettings ?? throw new ArgumentNullException(nameof(connectionSettings));
        _connection = GetConnection();
    }

    public IModel Create()
    {
        return _connection.CreateModel();
    }

    public bool Return(IModel obj)
    {
        if (obj.IsOpen)
            return true;

        obj?.Dispose();
        return false;
    }

    private IConnection GetConnection()
    {
        try
        {
            var conFactory = new ConnectionFactory
            {
                HostName = _connectionSettings.Value.HostName,UserName = _connectionSettings.Value.UserName,Password = _connectionSettings.Value.Password,VirtualHost = _connectionSettings.Value.VirtualHost,DispatchConsumersAsync = _connectionSettings.Value.DispatchConsumersAsync,AutomaticRecoveryEnabled = _connectionSettings.Value.AutomaticRecoveryEnabled
            };

            if (_connectionSettings.Value.Port != null)
                conFactory.Port = _connectionSettings.Value.Port.Value;

            return conFactory.CreateConnection();
        }
        catch (Exception e)
        {
            _logger.LogError("Error while trying to connect to RabbitMq server",e);
            throw;
        }
    }
}

使用对象池的发布者:

    public class Publisher : IPublishRabbitMessages
{
    private readonly ILogger<Publisher> _logger;
    private readonly IHandlePublisherConfirm _publisherConfirmHandler;
    private readonly IConfigureRabbitQueue _queueConfiguration;
    private readonly IOptions<RabbitQueueSettings> _queueSettings;

    private volatile bool _configuredSuccessfully;
    private readonly DefaultObjectPool<IModel> _objectPool;

    public Publisher(
        ILogger<Publisher> logger,IPooledObjectPolicy<IModel> objectPolicy,IConfigureRabbitQueue queueConfiguration,IOptions<RabbitQueueSettings> queueSettings,IHandlePublisherConfirm publisherConfirmHandler)
    {
        _logger = logger ?? throw new ArgumentNullException(nameof(logger));
        _objectPool = new DefaultObjectPool<IModel>(objectPolicy ?? throw new ArgumentNullException(nameof(objectPolicy)),Environment.ProcessorCount * 2);
        _queueConfiguration = queueConfiguration ?? throw new ArgumentNullException(nameof(queueConfiguration));
        _queueSettings = queueSettings ?? throw new ArgumentNullException(nameof(queueSettings));
        _publisherConfirmHandler = publisherConfirmHandler ??
                                   throw new ArgumentNullException(nameof(publisherConfirmHandler));

        DoConfigure(_objectPool.Get());
    }

    public bool ConfiguredSuccessfully => _configuredSuccessfully;

    public void BasicPublish<T>(IPublishMessageOptions<T> options) where T : class
    {
        if (!_configuredSuccessfully)
            return;

        var channel = _objectPool.Get();

        try
        {
            var properties = channel.CreateBasicProperties();
            properties.Persistent = options.Persistent;

            var json = JsonConvert.SerializeObject(options.BodyObject);
            var body = Encoding.UTF8.GetBytes(json);

            _publisherConfirmHandler.AddOutstandingConfirm(channel.NextPublishSeqNo,json);
            channel.BasicPublish(options.Exchange,options.RoutingKey,properties,body);
        }
        catch (Exception e)
        {
            _logger.LogError("Error while publishing data to rabbit queue",e);
            throw;
        }
        finally
        {
            _objectPool.Return(channel);
        }

    }

    public void DoConfigure(IModel channel)
    {
        try
        {
            _queueConfiguration.CreateQueue(channel,_queueSettings.Value);

            channel.ConfirmSelect();

            channel.BasicAcks += (sender,ea) =>
                _publisherConfirmHandler.CleanOutstandingConfirms(ea.DeliveryTag,ea.Multiple);

            channel.BasicNacks += (sender,ea) => _publisherConfirmHandler.HandleNack(ea.DeliveryTag);

            _configuredSuccessfully = true;
        }
        catch (Exception e)
        {
            _logger.LogError($"{nameof(Publisher)} could not be configured properly with following error message : {e.Message}",e);
            throw;
        }
        finally
        {
            _objectPool.Return(channel);
        }
    }
}

以及发布者用于处理确认的发布者确认处理程序:

    public class PublisherConfirmHandler : IHandlePublisherConfirm
{
    private readonly ILogger<PublisherConfirmHandler> _logger;
    protected readonly ConcurrentDictionary<ulong,string> OutstandingConfirms;

    public PublisherConfirmHandler(ILogger<PublisherConfirmHandler> logger)
    {
        _logger = logger ?? throw new ArgumentNullException(nameof(logger));
        OutstandingConfirms = new ConcurrentDictionary<ulong,string>();
    }

    public void CleanOutstandingConfirms(ulong sequenceNumber,bool multiple)
    {
        if (multiple)
        {
            var confirmed = OutstandingConfirms.Where(k => k.Key <= sequenceNumber);
            foreach (var entry in confirmed)
                OutstandingConfirms.TryRemove(entry.Key,out _);
        }
        else
        {
            OutstandingConfirms.TryRemove(sequenceNumber,out _);
        }
    }

    public void AddOutstandingConfirm(ulong sequenceNumber,string body)
    {
        OutstandingConfirms.TryAdd(sequenceNumber,body);
    }

    public void HandleNack(ulong sequenceNumber)
    {
        var successful = OutstandingConfirms.TryGetValue(sequenceNumber,out var body);

        _logger.LogCritical($"Message with body {body} has been nack-ed. Sequence number : {sequenceNumber}");
    }
}

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-