Bug 981341 - Add CLI operations to start/stop MDB delivery
Summary: Add CLI operations to start/stop MDB delivery
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER1
: EAP 6.2.0
Assignee: Jeff Mesnil
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-04 13:50 UTC by Ravi Bhardwaj
Modified: 2018-12-05 16:09 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:23:22 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-878 0 Major Resolved Message-Driven Beans doesn't support DeliveryActive activation config property 2016-06-06 15:35:58 UTC

Internal Links: 981348

Description Ravi Bhardwaj 2013-07-04 13:50:24 UTC 
Description of problem:

startDelivery()/stopDelivery() missing in EAP 6 which were available using JMX in EAP 5.x.
Comment 2 JBoss JIRA Server 2013-07-05 14:00:51 UTC 
Jeff Mesnil <jmesnil> made a comment on jira WFLY-878

PR merged in master branch
Comment 3 Rostislav Svoboda 2013-07-08 08:06:03 UTC 
This is new functionality, please target it for EAP 6.2.
Comment 12 Jan Martiska 2013-09-18 14:14:44 UTC 
Experimented with this manually in 6.2.0.ER1.
It seems to work well and provided tests are passing. Setting to VERIFIED.
Comment 16 Scott Mumford 2013-11-25 05:08:51 UTC 
Added draft release note in Doc Text field and marked for inclusion in Release Notes document.

Including original text here for reference:

Features: 

Add DeliveryActive activation config property that is used only for the MDB component creation to activate or deactive message delivery.

The management operations :start-delivery & :stop-delivery (and the delivery-active runtime read-only attribute) can be used to start/stop delivery on the MDB resource (under /deployment=<deployment_name>/subsystem=ejb3/message-driven-bean=<mdb_name>).

By default, the MDB is started and delivery of messages occurs as soon as the MDB is deployed

Reasons: 

Result (if any):
Note You need to log in before you can comment on or make changes to this bug.