[
https://issues.apache.org/jira/browse/QPID-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-4521.
------------------------------
Resolution: Fixed
Hi Robbie,
I've reviewed your change and I have no comments. I did wonder if we ought to
have a little more debug logging around QueueEntryImpl.routeToAlternate() might
be helpful?
Perhaps a debug logging statement to log - if the message has been routed to a
queue(s) on the alternate exchange, or queues on the alternate's alternate
exchange, or nowhere at all.
What do you think?
> [Java broker] routing to an alternate exchange during queue deletion fails
> for topic exchanges.
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-4521
> URL: https://issues.apache.org/jira/browse/QPID-4521
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.16, 0.18, 0.20
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.21
>
>
> Routing to an alternate exchange during queue deletion fails for topic
> exchanges. This is because the InboundMessageAdapter used to adapt the queues
> QueueEntry for routing by the exchange has a defect in the
> getRountingKeyShortSring() method. This method returns an AMQShortString and
> is used by the Topic exchange (to avoid redoing much of the Topic matching
> logic that uses AMQShortString) whereas the other exchanges use the
> getRoutingKey() method which returns a String.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
