On 01/29/2016 11:50 PM, jjw tectec wrote:
I ran the following script to set up a dynamic exchange route from Bs to
B1.
EX=TestExchange
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bs add exchange topic $EX
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add exchange topic $EX
~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d dynamic add $B1 $Bs $EX
Afterwards, I stopped the destination broker B1, but then B1 won't run
again, even after I rebuilt & reinstalled everything...
The errors I see from the broker log was about broker B1 not being able to
find the exchange that I created above. The exchange wasn't durable, why
would B1 try to look for it anyway?
2016-01-29 17:41:07 [Broker] error Link connection to XXX.XXX.XXX.246:5673
failed: Unsupported transport type: tcp
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:1363)
2016-01-29 17:41:07 [Broker] critical Broker (pid=2553) start-up failed:
not-found: Exchange not found: TestExchange
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/ExchangeRegistry.cpp:144)
2016-01-29 17:41:07 [Store] info Linear Store: Journal "TplStore":Destroyed
2016-01-29 17:41:07 [Broker] notice Broker (pid=2553) shut-down
2016-01-29 17:41:07 [Broker] critical Unexpected error: not-found: Exchange
not found: TestExchange
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/ExchangeRegistry.cpp:144)
This seems to be a bug to me...
Yes, I would agree that is a bug. As suggested in the first response,
this is most likely a result of the router being durable and the
exchange not,so the workaround is simply to declare both durable or
neither. However I would agree that it shouldn't prevent restart anyway,
so feel free to raise a JIRA and we'll try and get that fixed.
To proceed you would need to delete the store first.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
