PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'exchange' in vhost '/': received 'direct

最新推荐文章于 2023-07-19 09:34:55 发布

转载最新推荐文章于 2023-07-19 09:34:55 发布 · 4.2k 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/wang-yaz/p/10980607.html

文章标签：

#大数据

本文记录了在使用RabbitMQ过程中遇到的PRECONDITION_FAILED错误的解决方法，当exchange类型不匹配时，需在web界面的Exchanges模块中删除原有exchange。

最近在搞rabbitmq，把解决问题方法记下

问题1：PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'exchange' in vhost '/': received 'direct

问题2：如下图

原因：一旦创建了exchange, RabbitMQ是不允许对其改变的,不然会报错

解决方法：

在web上Exchanges模块把之前的exchange删除。

转载于:https://www.cnblogs.com/wang-yaz/p/10980607.html

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

adviceuser2014

关注关注

1
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

rabbitmq报错：PRECONDITION_FAILED - parameters for queue ‘test-1‘ in vhost ‘/‘ not equivalent

己亥谷雨

09-07

1567

错误如下： [root@master2 rabbitmq-python]# python send-1.py Traceback (most recent call last): File "send-1.py", line 9, in <module> channel.queue_declare(queue='test-1') File "/usr/lib/python2.7/site-packages/pika/adapters/blocking_connection.

PRECONDITION_FAILED - inequivalent arg ‘type‘ for exchange ‘exchange‘ in vhost ‘/‘: received ‘direct

qq_32814555的博客

11-13

3017

https://www.cnblogs.com/wang-yaz/p/10980607.html

参与评论您还未登录，请先登录后发表或查看评论

springboot 项目启动报错（RabbitMQ问题）

weixin_43824748的博客

03-19

3974

记一次项目启动报错（Springboot）Shutdown Signal: channel error; protocol method: #methodShutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg ‘type’ for exchange ‘exchangeName’

rabbitmq系列问题解决：406, “PRECONDITION_FAILED - inequivalent arg ‘durable‘

asdfgh0077的博客

05-11

1361

rabbitmq系列问题解决：406, "PRECONDITION_FAILED - inequivalent arg 'durable'

inequivalent arg ‘type‘ for exchange ‘xxx‘ in vhost ‘/‘: received ‘direct‘ but current is ‘fanout‘,

Bab的博客

11-02

7366

使用RabbitMQ时出现类似错误inequivalent arg 'type' for exchange 'xxx' in vhost '/': received 'direct' but current is 'fanout', class-id=40, method-id=10)，出现此错误提示的原因是名为为"xxx"的这个exchange已经存在且为"广播"类型，现在尝试将其修改为"定向推送"，RabbitMQ中一旦创建了exchange是不允许对其改变的，如果尝试对其进行变更就会出现此错误提示，如

Shutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-dead-letter-exchange' for queue 'wechat.payment.queue' in vhost 'yltMall': received the value 'dlx.exchange'

08-27

PRECONDITION_FAILED - inequivalent arg 'x-dead-letter-exchange' for queue 'wechat_payment_queue' in vhost '/': received 'dlx_exchange_new' but current is 'dlx_exchange_old' ``` ### 解决方案 1. **...

channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'retry.exchange' in vhost 'extension': received 'fanout' but current is 'direct', class-id=40, method-id=10)

08-10

在 RabbitMQ 中，`PRECONDITION_FAILED - exchange type mismatch` 错误通常表示尝试声明一个已经存在的交换机（Exchange），但新声明的交换机类型与之前声明的类型不一致。例如，如果一个名为 `my_exchange` 的...

Shutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'TOPIC.STOREMASTER.INFO' in vhost 'rdp': received 'topic' but current is 'fanout', class-id=40, m

04-27

当出现`PRECONDITION_FAILED - inequivalent arg 'type' for exchange`错误时，表明客户端尝试声明的Exchange参数与服务器已存在的Exchange参数不兼容。以下是具体原因及解决方法： --- #### 错误原因分析 1. **...

ERROR 33476 --- [68.195.101:5672] o.s.a.r.c.CachingConnectionFactory : Shutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'trade.delay.direct' in vhost '/hmall': received ''x-delayed-message'' but current is 'direct', class-id=40, method-id=10)

最新发布

09-26

首先，用户的问题是：解决RabbitMQ错误：PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'trade.delay.direct' in vhost '/hmall': received ''x-delayed-message'' but current is 'direct'。...

inequivalent arg ‘type‘ for exchange ‘zncz‘ in vhost ‘/‘: received ‘direct‘ but current is ‘topic‘

qq_43780402的博客

07-19

967

"zncz"这个交换机已经创建在rabbitmq中了并且类型为topic，但是在spingboot客户端定义的交换类型为direct，所以产生了冲突，所以需要修改springboot中定义的客户端的类型为topic。问题：inequivalent arg 'type' for exchange 'zncz' in vhost '/': received 'direct' but current is 'topic'

耗子叔ARTS：第十一周

csdn_subaodong的博客

06-22

454

耗子叔ARTS：第十一周 Algorithm: /*** 给定字符串J代表石头中宝石的类型，和字符串S代表你拥有的石头。S中每个字符代表了一种你拥有的石头的类型，你想知道你拥有的石头中有多少是宝石。* <p>* J中...

rabbitMq 常见问题

lxw1844912514的博客

02-22

3661

1.Server channel error: 406, message: PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'delay-lxw' in vhost '/': received 'false' but current is 'true' 这是由于服务端和客户端设置的交换机类型不一致所致 rabbitmq的exchange有以下几种类型： fanout类型 (广播) direct..

RabbitMQ报错 received ‘topic‘ but current is ‘direct‘

私欲日生，如地上尘，一日不扫，便又有一层。着实用功，便见道无终穷，愈探愈深，必使精白无一毫不彻方可。

07-27

2257

翻译过来就是收到'topic'，但当前是'direct。

RabbitMQ消费者端报错，找不到Exchange

wj_phm的博客

08-17

1997

NOT_FOUND - no exchange， channel.queueBind, channel.exchangeBind

RabbitMq报错解决

有一颗前端心的后端开发小哥

04-02

6170

RabbitMq报错解决错误一：java远程连接rabbitMQ服务报错com.rabbitmq.client.ShutdownSignalException: connection error错误二：ShutdownSignalException:channel error； protocol method 最近想搭建mq服务器，自己玩一下，结果惨不忍睹，在此记录下出现的问题以及解决方案。❥(^_-) 本篇博文参考大佬，链接如下： https://www.freesion.com/article/3977

RabbitMQ学习之四:发布/订阅(direct方式)

xubingchuan_blog的博客

12-18

7616

参考http://blog.csdn.net/lmj623565791/article/details/37620057和RabbitMQ官网,加之自己部分修改和实验,因是新手自学,难免有不对之处,欢迎大家指正,小弟先谢过了.这篇文章主要学习下exchange类型的第二种类型:direct在上一篇文章中,主要学习了RabbitMQ exchange的fanout(广播方式),即producer发送的

Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'type' for exchange 'SYSTEM_USER_OPERATION_EXCHANGE' in vhost '/': receiv

04-28

当出现 `ShutdownSignalException PRECONDITION_FAILED` 错误且提示 `inequivalent arg 'type' for exchange` 时，根本原因是尝试声明的 exchange 参数与 RabbitMQ 服务器上已存在的同名 exchange 属性不一致[^2]。...