我这边的使用场景:多名用户进行同一操作。
(具体一点:我这边的系统哦,数据库用的是mysql,操作是导入excel,可以这么说百分之六十的页面都有批量导入,而且一个页面不止一个批量导入按钮,多的有六个批量导入按钮。可想而知,同时操作!恍恍惚惚o(╥﹏╥)o)
基础配置
public ConnectionFactory rabbitmqFactory; private string hostName = Model.AppConfigurtaionServices.Configuration["AppSettings:RabHost"];//RabbitMq网址 private string userName = Model.AppConfigurtaionServices.Configuration["AppSettings:RabUserName"];//RabbitMq用户名 private string pwd = Model.AppConfigurtaionServices.Configuration["AppSettings:RabPwd"];//RabbitMq密码 private int port = int.Parse(Model.AppConfigurtaionServices.Configuration["AppSettings:RabPort"]);//RabbitMq端口 /// <summary> /// 构造函数 /// </summary> public RabbitMqUtil() { rabbitmqFactory = new ConnectionFactory() { HostName = hostName, UserName = userName, Password = pwd, Port = port, AutomaticRecoveryEnabled = true, }; } /// <summary> /// 创建工厂 /// </summary> public RabbitMqUtil(string hostName, string userName, string pwd, int port) { rabbitmqFactory = new ConnectionFactory() { HostName = hostName, UserName = userName, Password = pwd, Port = port, RequestedHeartbeat = TimeSpan.FromSeconds(100), AutomaticRecoveryEnabled = true //ContinuationTimeout= TimeSpan.FromSeconds(3000) }; }
生产端代码
/// <summary> /// 生产端 /// </summary> /// <param name="exchangeName">交换机名称</param> /// <param name="queueName">队列名称</param> /// <param name="routeKey">路由关键字</param> /// <param name="msg">消息内容</param> public void Producter(string exchangeName, string queueName, string routeKey, string msg) { IConnection conn = rabbitmqFactory.CreateConnection(); IModel model = conn.CreateModel(); //设置交换器的类型 model.ExchangeDeclare(exchangeName, ExchangeType.Direct, durable: true, autoDelete: false, arguments: null); //声明一个队列,设置队列是否持久化,排他性,与自动删除 model.QueueDeclare(queueName, durable: true, exclusive: false, autoDelete: false, arguments: null); //绑定消息队列,交换器,routingkey model.QueueBind(queueName, exchangeName, routingKey: routeKey); model.ConfirmSelect(); var props = model.CreateBasicProperties(); props.ContentType = "text/plain"; props.ContentEncoding = "UTF-8"; props.DeliveryMode = 1;// 设置消息是否持久化,1: 非持久化 2:持久化 var mes = Encoding.UTF8.GetBytes(msg); model.BasicPublish(exchangeName, routingKey: routeKey, basicProperties: props, body: mes); } /// <summary> /// 生产端(死信) /// </summary> /// <param name="exchangeName">交换机名称</param> /// <param name="queueName">队列名称</param> /// <param name="routeKey">路由关键字</param> /// <param name="deadLetterExchangeName">死信交换机名称</param> /// <param name="deadLetterQueueName">死信队列名称</param> /// <param name="deadLetterRouting">死信路由关键字</param> /// <param name="msg">消息内容</param> public void DeadProducter(string exchangeName, string queueName, string routeKey, string deadLetterExchangeName, string deadLetterQueueName, string deadLetterRouting, string msg) { IConnection conn = rabbitmqFactory.CreateConnection(); IModel model = conn.CreateModel(); //死信队列设置 Dictionary<string, object> dic = new Dictionary<string, object>(); dic.Add("x-dead-letter-exchange", deadLetterExchangeName);//死信交换器 dic.Add("x-dead-letter-routing-key", deadLetterRouting);//列信路由 dic.Add("x-message-ttl", 1000 * 60 * 2);//过期时间 //设置交换器的类型 model.ExchangeDeclare(exchangeName, ExchangeType.Direct, durable: true, autoDelete: false, arguments: null); //声明一个队列,设置队列是否持久化,排他性,与自动删除 model.QueueDeclare(queueName, durable: true, exclusive: false, autoDelete: false, arguments: dic); //绑定消息队列,交换器,routingkey model.QueueBind(queueName, exchangeName, routingKey: routeKey); model.ConfirmSelect(); var props = model.CreateBasicProperties(); props.ContentType = "text/plain"; props.ContentEncoding = "UTF-8"; props.DeliveryMode = 1;// 设置消息是否持久化,1: 非持久化 2:持久化 var mes = Encoding.UTF8.GetBytes(msg); model.BasicPublish(exchangeName, routingKey: routeKey, basicProperties: props, body: mes); }
消费端是写成控制台程序单独执行,就不po代码了~
原文地址:http://www.cnblogs.com/MuZiLily/p/16843798.html
1. 本站所有资源来源于用户上传和网络,如有侵权请邮件联系站长!
2. 分享目的仅供大家学习和交流,请务用于商业用途!
3. 如果你也有好源码或者教程,可以到用户中心发布,分享有积分奖励和额外收入!
4. 本站提供的源码、模板、插件等等其他资源,都不包含技术服务请大家谅解!
5. 如有链接无法下载、失效或广告,请联系管理员处理!
6. 本站资源售价只是赞助,收取费用仅维持本站的日常运营所需!
7. 如遇到加密压缩包,默认解压密码为"gltf",如遇到无法解压的请联系管理员!
8. 因为资源和程序源码均为可复制品,所以不支持任何理由的退款兑现,请斟酌后支付下载
声明:如果标题没有注明"已测试"或者"测试可用"等字样的资源源码均未经过站长测试.特别注意没有标注的源码不保证任何可用性