Bug 981341
| Summary: | Add CLI operations to start/stop MDB delivery | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ravi Bhardwaj <rbhardwa> |
| Component: | EJB | Assignee: | Jeff Mesnil <jmesnil> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | bmaxwell, ehugonne, eric.hubert, jmartisk, jmesnil, klape, rdickens, sjadhav, smumford |
| Target Milestone: | ER1 | ||
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
This release of JBoss EAP 6 includes a new *DeliveryActive* activation configuration property that is used only for the Message Driven Beans (MDB) component to activate or deactivate message delivery.
The management operations *:start-delivery* and *:stop-delivery* (and the read-only *delivery-active* runtime attribute) can now be used to start and stop delivery on the MDB resource (under */deployment=<deployment_name>/subsystem=ejb3/message-driven-bean=mdb_name>*).
By default, the new property is activated and delivery of messages occurs as soon as the MDB is deployed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:23:22 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: | |
| Embargoed: | |||
|
Description
Ravi Bhardwaj
2013-07-04 13:50:24 UTC
Jeff Mesnil <jmesnil> made a comment on jira WFLY-878 PR merged in master branch This is new functionality, please target it for EAP 6.2. Experimented with this manually in 6.2.0.ER1. It seems to work well and provided tests are passing. Setting to VERIFIED. 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): |