Bug 1142619
| Summary: | Removing jndi entry which does not exist return success in CLI | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> |
| Component: | JMS | Assignee: | Jeff Mesnil <jmesnil> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Miroslav Novak <mnovak> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.0 | CC: | kkhan |
| Target Milestone: | DR2 | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 12:40:40 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: | |||
Verified in EAP 6.4.0.DR2. Thanks, Jeff! |
Description of problem: Operation "remove-jndi" on queue/topic is successful when trying to remove non-existent JNDI entry: [standalone@localhost:9999 jms-queue=testQueue1] :read-resource { "outcome" => "success", "result" => { "durable" => true, "entries" => ["java:jboss/exported/jms/queue/testQueue2"], "selector" => undefined } } [standalone@localhost:9999 jms-queue=testQueue1] :remove-jndi(jndi-binding=java:jboss/exported/jms/queue/dummyQueue) { "outcome" => "success", "result" => undefined } We should return outcome "failed" with "failure-description" like "Can not remove JNDI name java:jboss/exported/jms/queue/dummyQueue. The resource does not contain such a JNDI name."