[
https://issues.apache.org/jira/browse/QPID-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed QPID-2494.
----------------------------
Resolution: Not A Problem
The issue here is that the address option used is wrong. It is node not
node-properties. I have created another jira to cover fixing the undesirable
behaviour by which such errors are simply ignored:
https://issues.apache.org/jira/browse/QPID-2497
> Node assertions don't work for node-property types ( topic, queue )
> --------------------------------------------------------------------
>
> Key: QPID-2494
> URL: https://issues.apache.org/jira/browse/QPID-2494
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Reporter: Jonathan Robie
>
> Asserting the wrong node property type seems to have no effect on address
> resolution in the drain example:
> $ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: topic
> }}"
> $ ./drain -a "amq.direct/foo; { assert: always, node-properties: { type: queue
> }}"
> $ ./drain -a "amq.fanout; { assert: always, node-properties: { type: queue }}"
> $ ./drain -a "amq.fanout; { assert: always, node-properties: { type: topic }}"
> The program seems to actually resolve the address, and can receive messages,
> even if the assertion does not match, and this is not limited to pre-declared
> exchanges:
> $ ./drain -a "fanout-exchange; { assert: always, node-properties: { type:
> queue
> }}" -t 30
> Message(properties={spout-id:1f32f14f-8cff-4a51-8bed-bac7fe84f00e:0},
> content='')
> It doesn't work for assertions on queues, either:
> $ ./drain -a "xoxox; { assert: always, node-properties: { type: topic }}"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
