RabbitMQ 3.12.6 API returns incorrect json result #10156
-
Describe the bugThe API '/api/queues' returns queue item array [], instead of expected json. Expected:
Actual:
As a result, the management web portal throws error:
Reproduction steps
Or, open the management portal, it shows error
Expected behavior
Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
Without a specific It could be an Erlang-specific JSON serialization problem where an empty proplist (a list of pairs) and a regular list (a JSON array) are indistinguishable, so an empty JSON object is serialized as an empty list. We have to specifically handled that in multiple places. However, we cannot tell with most of data elided in the examples. It also matters if the queues have emitted all stats at least once, or they have just been created and most stats are simply not available yet. So, please provide a specific set of steps we can use to reproduce. It is also important to know if this happens just on the first request or two, or is persistent. |
Beta Was this translation helpful? Give feedback.
-
Just to confirm, issue presists even if move to 3.13.0-rc.2-management |
Beta Was this translation helpful? Give feedback.
-
We cannot address what we do not know how to reproduce even some of the
time.
Does rabbitmqctl list_queues —formatter=pretty_table display various
columns differently from other clusters?
Can a cluster definitions file and a filtered query HTTP API response be
shared? You can see what the response is in browser developer tools.
Don’t forget to edit out the credentials in both the definitions file and
any API request examples
…On Fri, 15 Dec 2023 at 11:56, Steven.Xi ***@***.***> wrote:
Just to confirm, issue presists even if move to 3.13.0-rc.2-management
<https://hub.docker.com/layers/library/rabbitmq/3.13.0-rc.2-management/images/sha256-a6388040701297c2be13c37d1f5a3369f2782d33386a8ae6d9d02a2c31bc10f3?context=explore>
—
Reply to this email directly, view it on GitHub
<#10156 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAIQV62AUKJ7QAVTA6RFLYJR6M5AVCNFSM6AAAAABAWME22KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNRWGE3TS>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
|
Beta Was this translation helpful? Give feedback.
-
@stevenxi if you can reproduce this in a test environment, feel free to zip up RabbitMQ's data directories and attach them here. That should allow us to easily reproduce the issue. |
Beta Was this translation helpful? Give feedback.
-
Sorry guys, really can't reproduce in a testing environment. We decided no to use the management portal. Closing the issue. |
Beta Was this translation helpful? Give feedback.
@stevenxi if you can reproduce this in a test environment, feel free to zip up RabbitMQ's data directories and attach them here. That should allow us to easily reproduce the issue.