You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/08 23:38:59 UTC
[jira] [Resolved] (APLO-111) Inconsistent data reported by the REST
API (ghost queue)
[ https://issues.apache.org/jira/browse/APLO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-111.
--------------------------------
Resolution: Cannot Reproduce
Assignee: Hiram Chirino
Closing since we can't reproduce.
> Inconsistent data reported by the REST API (ghost queue)
> --------------------------------------------------------
>
> Key: APLO-111
> URL: https://issues.apache.org/jira/browse/APLO-111
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-web
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira