[QPID-4874] Alternate exchange unable to set from REST

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20
• Fix Version/s: 0.29
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Michal Zerola
• Created: 22/May/13 08:50
• Updated: 26/Sep/14 15:43
• Resolved: 18/Jul/14 19:21

Description

This is a follow-up on the discussion started on:

http://mail-archives.apache.org/mod_mbox/qpid-users/201303.mbox/%3CCAFitrpTiPo_yMhitGBM-1=QiW8xnKz3O2tqgSP3xbooDDC=[e-mail]%3E

I haven't seen any JIRA covering this issue yet. Setting an alternate exchange on the exchange is not possible now from the REST interface (e.g. using curl / web management).

The only way how one can set an alternate exchange is using the proper address from the JMS client and passing it to the MessageProducer:

"ADDR:test-exch; {create: always, node:{type: topic,x-declare: {alternate-exchange:'amq.fanout'}}}"

The exchange test-exch will then keep reference to the alternate exchange amq.fanout. However, listing the exchange using the curl will fail (produce endless output). I assume that the problem is caused by Json mapper, having problems to write object which is not ConfiguredObject (in this case it is FanoutExchange). This problem is reproducible by creating the exchange with alternate exchange reference using the address above and listing the exchange(s) with curl command. I think the solution can be to return the alternate exchange name (and not an object) from the ExchangeAdapter.java as I illustrated in the attached patch.

Thank you,

Michal

Issue Links

• relates to: QPID-5205 Viewing an exchange with alternate exchange through the Management UI causes exception in Broker logs.