Bug 1012451

Summary:	Core queues are not visible in destinations listing
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Martin Svehla <msvehla>
Component:	Web Console	Assignee:	Heiko Braun <hbraun>
Status:	CLOSED EOL	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	brian.stansberry, hpehl, jkudrnac, mnovak, msvehla, myarboro
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:44:15 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Svehla 2013-09-26 13:41:35 UTC

Description of problem:
HornetQ has two queue types - core and jms. Destination listing (in both Profile -> Messaging -> Destinations and Runtime -> Subsystems -> JMS Destinations) shows only JMS queues. It's also not possible to create new core queue in Profile.

In the management model, jms queues are in /subsystem=messaging/hornetq-server=*/jms-queue=* while core queues are in /subsystem=messaging/hornetq-server=*/queue=*

Version-Release number of selected component (if applicable):
EAP 6.2.0.ER3

How reproducible:
Create new core queue in configuration xml or in cli. New queue is not listed in the queue listings.

Expected results:
Both Profile and Runtime destination listings should list core queues and user should be able to create new core queue in Profile.

Comment 1 Heiko Braun 2013-10-21 11:38:01 UTC

out of scope for 6.2: it's a new feature and we are already beyond this point.

Comment 4 Harald Pehl 2015-09-17 15:09:17 UTC

I'd like to defer this to the next version.

Comment 5 JBoss JIRA Server 2016-05-16 18:19:40 UTC

Claudio Miranda <claudio.br> updated the status of jira HAL-225 to Coding In Progress

Comment 6 JBoss JIRA Server 2016-05-20 19:15:05 UTC

Harald Pehl <hpehl> updated the status of jira HAL-225 to Resolved