activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (Commented) (JIRA)" <>
Subject [jira] [Commented] (APLO-111) Inconsistent data reported by the REST API (ghost queue)
Date Sat, 28 Jan 2012 10:35:10 GMT


Hiram Chirino commented on APLO-111:

Hi Lionel,

You still seeing the same thing with the 1.0 RC? There queue cleanup bugs that were found
and squashed in 1.0 but I'm not sure if they would have caused this ghost queue issue in the
management APIs.
> Inconsistent data reported by the REST API (ghost queue)
> --------------------------------------------------------
>                 Key: APLO-111
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-web
>            Reporter: Lionel Cons
>             Fix For: 1.1
> In some cases, the data reported by the REST interface is inconsistent. The problem that
we have detected is with queues but it may be present elsewhere.
> In short, /broker/virtual-hosts/<vhost> reports a queue that cannot be accessed
via /broker/virtual-hosts/<vhost>/queues/<name>. In the web console, we get broken
links (404 errors).
> This may be linked to auto deletion (auto_delete_after parameter) but this is not a transient
error. After failing to get to the queue data, we still see the queue name listed at virtual
host level. It's not a problem of browser caching as we see the same thing with wget.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message