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
The response to /api/queues/%2f/{queuename} has a consumer_details array of objects, where one of the fields is channel_details.
This field is an object if filled, but an empty array when no data is available.
In most cases the consumer_details array is empty, or there is a consumer and the channel_details are filled, but occasionally the a consumer_detail is returned with empty channel_details. I am using C# and the Json deserializer cannot handle the array where it expects an object.
The problem occurs in a test setup where consumers are short-lived. The behavior causes a highly unreliable test result.
RabbitMq version is 3.8.9, before this version we used 3.7.19 where we did not experience this problem.
The text was updated successfully, but these errors were encountered:
Because of rabbitmq/rabbitmq-server#2684, in
all RabbitMQ versions until 3.11.8, the
`.consumer_details.channel_details` attribute for a queue could be
sent as an empty array (`[]`) instead an empty object (`{}`).
This PR provides a fix to that by customizing the json serializarion
of ChannelDetails.
The response to /api/queues/%2f/{queuename} has a consumer_details array of objects, where one of the fields is channel_details.
This field is an object if filled, but an empty array when no data is available.
In most cases the consumer_details array is empty, or there is a consumer and the channel_details are filled, but occasionally the a consumer_detail is returned with empty channel_details. I am using C# and the Json deserializer cannot handle the array where it expects an object.
The problem occurs in a test setup where consumers are short-lived. The behavior causes a highly unreliable test result.
RabbitMq version is 3.8.9, before this version we used 3.7.19 where we did not experience this problem.
The text was updated successfully, but these errors were encountered: