Bug 1004789
| Summary: | attributes on messaging queue should be read-only | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| 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: | Russell Dickenson <rdickens> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1.1 | CC: | brian.stansberry, csuconic, jmesnil | ||||||
| Target Milestone: | ER3 | ||||||||
| Target Release: | EAP 6.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-12-15 16:23:17 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Miroslav Novak
2013-09-05 13:40:18 UTC
there is no attached reproducer.zip Created attachment 797223 [details]
reproducer.zip
where are the source of the attached client.jar? Created attachment 797258 [details]
client-maven-project.zip
It's using dependency from our engineering repo where you probably don't have access but you can still specify different dependencies for this client.
Used classes:
org.jboss.jms.client.TestProducer
org.jboss.jms.client.TestConsumer
(In reply to Miroslav Novak from comment #0) > - In CLI run following commands: > /subsystem=messaging/hornetq-server=default/jms-queue=testQueue: > add(durable=true, > entries=["java:jboss/exported/jms/queue/testQueue","jms/queue/testQueue"]) > /subsystem=messaging/hornetq-server=default/jms-queue=testQueue:write- > attribute(name=selector,value="color='RED'") The test setup is not correct. You add a JMS queue *without* a selector. When you write the selector attribute, please not that the server replied that a reload is required: /subsystem=messaging/hornetq-server=default/jms-queue=testQueue:write-attribute(name=selector,value="color='RED'") { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } That's why your consumer receives all the message: the server has not been reloaded and the selector you added has not been taken into account. If you change the test setup to add the queue with the selector, your consumer will receive only the filtered out message: /subsystem=messaging/hornetq-server=default/jms-queue=testQueue:add(durable=true, entries=["java:jboss/exported/jms/queue/testQueue","jms/queue/testQueue"], selector="color='RED'") Thanks Jeff for feedback. You're right that when queue is added with selector then everything is ok and just 'RED' messages are received by consumer. If selector is specified after queue was created then I can see that consumer receives all messages. Reload or restart of server has no effect. Jeff Mesnil <jmesnil> made a comment on jira WFLY-2071 PR for master branch *** Bug 1004715 has been marked as a duplicate of this bug. *** Jeff Mesnil <jmesnil> made a comment on jira WFLY-2071 PR merged in master branch Verified in EAP 6.2.0.ER4. Attribute selector on queue is read-only now. Thanks Jeff for the change. |