Bug 1334932

Summary:	Providing a "name" for a HornetQ server prevents JMS statistics from displaying in web console
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	TJ Cowhey <tcowhey>
Component:	Web Console	Assignee:	jboss-set
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	chaowan, hbraun, hpehl, jkudrnac, msmerek, pjelinek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://c.na7.visual.force.com/apex/Case_View?id=500A000000U4Uq2IAF&sfdc.override=1
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-24 14:16:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description TJ Cowhey 2016-05-10 20:30:38 UTC

Description of problem:

When configuring HornetQ, if a server name is provided (<hornetq-server name="x">), JMS statistics are not displayed in the web console. CLI provides statistics no matter if a name is provided or not.

Not specifying a server name causes the server to take "default" as the name, and all statistics are displayed in the console.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Configure a Hornetq server with a name <hornetq-server name="x">
2. Start the server and attach a consumer or push messages to a JMS destination
3. Check the JMS statistics in the console

Actual results:

No stats

Expected results:

JMS stats displayed

Comment 1 Chao Wang 2016-05-10 23:41:35 UTC

This looks like a duplicated issue of https://bugzilla.redhat.com/show_bug.cgi?id=1293311 Can you please try with EAP 6.4.7 ?

Comment 2 TJ Cowhey 2016-05-11 12:01:13 UTC

Chao - you're right, this is the exact same issue.

Comment 3 Martin Šmérek 2016-05-24 13:47:20 UTC

TJ, if this issue is a duplicate, could you please close it? Thank you.

Comment 4 TJ Cowhey 2016-05-24 14:16:38 UTC


*** This bug has been marked as a duplicate of bug 1293311 ***