Bug 1079457 - removeJNDI is not exposed through JMX
Summary: removeJNDI is not exposed through JMX
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-21 15:33 UTC by Amine Belkoura
Modified: 2019-08-19 12:49 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:49:17 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3029 0 Major Closed add remove-jndi operations to JMS resources 2019-07-15 20:29:19 UTC

Description Amine Belkoura 2014-03-21 15:33:06 UTC 
Description of problem:

HornetQ JMS Destination MBean in EAP 5 exposes both addJNDI & removeJNDI methods through JNDI. However, removeJNDI does not appear to be exposed in EAP 6. 


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

EAP 6.2


How reproducible:


Steps to Reproduce:
1.Start an EAP instance, with a a configured JMS queue
2.Start jconsole, and go to the queue operations
3. addJNDI method is listed, but not removeJNDI
Comment 1 Miroslav Novak 2014-03-24 08:31:53 UTC 
Adding Jeff to cc. I think we already have bz/jira somewhere for this.
Comment 2 Jeff Mesnil 2014-03-24 08:33:20 UTC 
added upstream JIRA issue tracking this bug
Note You need to log in before you can comment on or make changes to this bug.