[
https://issues.apache.org/jira/browse/DISPATCH-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated DISPATCH-1418:
---------------------------------
Description:
When a message cannot be forwarded the message should be released.
However, when the forwarding treatment is "unavailable" that message must be
REJECTED (as per the description of the "unavailable treatment).
When the router tries to determine if the outcome should be RELEASED or
REJECTED it does not check for a matching router.config.address configuration
entity. This entity contains a treatment for the given address. If an address
configuration matches the address the treatment should come from the address
configuration - not the router default configuration.
To reproduce:
Configure a router with defaultTreatment set to unavailable.
Configure an address prefix that uses the "closest" treatment.
Attach a sender to the router using an anonymous link.
Send a message to an address that will match the configured address prefix
while there are no subscribers.
Expect: the message be RELEASED by the router
Actual: the message is REJECTED by the router
was:
Attach a sender to the router using an anonymous link.
Send a message to an address that is pre-configured (say "closest/foo") while
there are no subscribers.
Expect: the message be RELEASED by the router
Actual: the message is REJECTED by the router
See system_tests_router_mesh.py
> The default forwarding treatment is not overridden by the treatment in the
> address configuration
> ------------------------------------------------------------------------------------------------
>
> Key: DISPATCH-1418
> URL: https://issues.apache.org/jira/browse/DISPATCH-1418
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 1.8.0, 1.9.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
>
> When a message cannot be forwarded the message should be released.
> However, when the forwarding treatment is "unavailable" that message must be
> REJECTED (as per the description of the "unavailable treatment).
> When the router tries to determine if the outcome should be RELEASED or
> REJECTED it does not check for a matching router.config.address configuration
> entity. This entity contains a treatment for the given address. If an
> address configuration matches the address the treatment should come from the
> address configuration - not the router default configuration.
> To reproduce:
> Configure a router with defaultTreatment set to unavailable.
> Configure an address prefix that uses the "closest" treatment.
> Attach a sender to the router using an anonymous link.
> Send a message to an address that will match the configured address prefix
> while there are no subscribers.
> Expect: the message be RELEASED by the router
> Actual: the message is REJECTED by the router
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
