You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When transactionCoordinatorEnabled is true in standalone.conf,there is error consuming with pushing of RabbitMQ client,but it is normal that consuming with pulling.
To Reproduce
1、Open the transactionCoordinatorEnabled is true in standalone.conf
2、Open the aop feature normally
3、Start the standalone service
4、code of Rabbitmq as follows:
Describe the bug
When
transactionCoordinatorEnabled
istrue
in standalone.conf,there is error consuming with pushing of RabbitMQ client,but it is normal that consuming with pulling.The detailed logs is as following, the time of correct logs is 2023-12-04T10:34:18,946+0800, the time of wrong logs is 2023-12-04T10:38:40,748+0800.
The logs of Close and Open the transactionCoordinatorEnabled .log
broker-k8s.log
Version:3.0.0
Test environment: standalone
To Reproduce
1、Open the transactionCoordinatorEnabled is true in standalone.conf
2、Open the aop feature normally
3、Start the standalone service
4、code of Rabbitmq as follows:
Expected behavior
The Aop function is normal when
transactionCoordinatorEnabled
is true.Screenshots
The text was updated successfully, but these errors were encountered: