Bug 1278370 - [GSS] (6.4.z) start-delivery/stop-delivery operations are missing from MDB deployment in domain mode when using Console
Summary: [GSS] (6.4.z) start-delivery/stop-delivery operations are missing from MDB de...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: CR1
: EAP 6.4.5
Assignee: Dmitrii Tikhomirov
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On: 1266913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 11:02 UTC by Tom Ross
Modified: 2019-09-12 09:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1266913
Environment:
Last Closed: 2015-11-09 10:21:24 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-1111 0 Major Resolved Expose runtime methods in JMX for resources in domain servers 2017-08-24 22:42:34 UTC
Red Hat Issue Tracker WFLY-5418 0 Major Resolved start-delivery/stop-delivery operations descriptions are missing from MDB deployment in domain mode 2017-08-24 22:42:34 UTC

Comment 5 Vaclav Tunka 2015-11-09 10:21:24 UTC 

*** This bug has been marked as a duplicate of bug 1266913 ***
Comment 6 Jeff Mesnil 2015-11-09 10:33:20 UTC 
This issue was not a duplicate of #1266913.

EAP 6.4 does not expose RUNTIME_ONLY operations in JMX. This would be a new feature and this must be dealt appropriately. This does not only concern the start/stop-delivery operations but *any* RUNTIME_ONLY operations on resources in domain servers.

This BZ was created to make sure that the fix to expose start/stop-delivery in domain mode would be fixed independently and then we could use appropriate channel to decide to expose RUNTIME_ONLY operations in JMX  for EAP 6.
Comment 7 Vaclav Tunka 2015-11-09 10:39:08 UTC 
Thanks for the clarification Jeff, we will take this BZ to triage today to deal with it appropriately. I was wondering in upstream this was tracked only in single jira: WFLY-5418
Comment 8 Jeff Mesnil 2015-11-09 10:41:32 UTC 
sorry, I forgot to link the upstream issue (WFCORE-1111)
Note You need to log in before you can comment on or make changes to this bug.